Home > Articles > Web Services > XML

Why Hugh Grant Picked SOAP Over XML-RPC: An Interview with Cape Clear's CTO (Part 2 of 2)

Alex Nghiem (pictured, right) concludes his interview with Hugh Grant (left), CTO of Cape Clear, with a discussion of why SOAP proved to be more ubiquitous than XML-RPC. (Part 2 of 2)
Read Part 1 of this Interview here.
Like this article? We recommend

Alex: Your products include two features called SOAPDirect and UDDIDirect. Can you elaborate on their features?

Hugh: The goals of those tools were to provide developers with an ease-of-use library. We built a lot of our initial clients and demos using things like Apache SOAP and the IBM SOAP toolkits. While they're effective, they're quite complex. You need to be a pretty good developer to use these things to their fullest, and we thought, "Hey, we've got all this mapping technology. Why don't we actually just roll that out as a client toolkit?" The goal of SOAPDirect is to re-create in Java what Microsoft has done with Visual Basic—basically, make it really trivial to write SOAP clients. You don't need to know what types are being used; you can just pass arbitrary Java objects and the toolkit will work out on-the-fly what the correct mapping is from those types into SOAP. [The Hello World application] can run through a couple of hundred lines of code, if you're using something like Apache, and our goal is to have it down to 10 lines of code if you're using SOAPDirect.

UDDIDirect does the same thing for UDDI. It's basically a specialization of our SOAPDirect API, with some ease-of-use wrappers around the UDDI specs, because UDDI is quite complex. A lot of developers aren't going to be that technical. Web services are going to be [deployed to] a much wider audience than your usual Java developer, and so we want to make it easy for those people to access the key services.

Alex: Your products currently work with stateless session beans, but let's assume I already have an application that has a combination of stateless session beans and stateful session beans, along with entity beans. How would the migration work?

Hugh: Customers who have done this typically use either a wrapper or a Factory pattern and basically create a level of indirection between their stateful code and the system. A stateless session bean looks up the Factory or has a direct connection through to the back-end object or a component, and that works pretty well. We're restricted to a stateless model because of the way SOAP works. People who directly support stateful session beans or entity beans are doing it in proprietary ways, and you don't have interoperability at that level; we believe it's better (in the Java domain) to just write a wrapper to give you that functionality.

Alex: One of the key selling points of your products is ease of use over the existing toolkit. Can you elaborate on why XML-RPC didn't catch on, and SOAP is so much more ubiquitous?

Hugh: XML-RPC has quite a following at an open-source level, but it was never really picked up by any of the vendors. What's driving SOAP is the fact that you've got IBM, Sun, Oracle, and Microsoft for the first time on the same platform, saying, "We'll support this standard." The value of SOAP is its ubiquity. The ease of use is really shared with any other XML approach, so what's driving SOAP is Visual Studio .NET, J2EE 1.4, Oracle's SOAP support.

Alex: Are there any inherent technical limitations of XML-RPC that made it inferior to SOAP, or too limiting, so that it didn't become ubiquitous? Why did vendors decide to standardize on SOAP?

Hugh: The SOAP specs are more detailed and XML-RPC is more lightweight and generic. People like the extra depth they find in the SOAP specifications, and the fact that it's being filled out to include specifically how [XML] schemas work and different bindings; in the future, we'll see asynchronous support. The vendors invested in developing the specification, whereas XML-RPC was the work of a couple of people in the open source community—very good work, but it just didn't have commercial backing.

Alex: The web services model has several pieces: creation, consumption, registration, and deployment. Your product helps on consumption, creation, and to some degree registration. What deployment features does Cape Connect provide, since the existing standards don't currently address this issue?

Hugh: When people deploy web services, they usually follow quite a complex model—maybe something like the EJB deployment descriptor model. We wanted to make it easier. With Cape Connect, everything is dynamic and based on [Java] reflection. If you want to deploy a web service, you just have to register the WSDL file with Cape Connect, and then it knows how to do [the mapping].

The goal is to make deployment as easy as development. It's just a pushbutton exercise: You point our tools at your components and they're deployed. There's nothing extra you have to do. Internally we'll be running on top of whatever platform you're using—CORBA platform, J2EE platform. Internally, things will be CORBA components or Beans or Java classes. What we do is basically put a wrapper around that to insulate the user from all the details of how that's deployed. We do the hard work, so the user gets to have a really simple experience deploying web services.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020