RPC/DOC style Web services with a JAX-M client

RPC/DOC style Web services with a JAX-M client

How can one invoke a Java RPC/DOC-style or a .NET RPC/DOC-style Web services using a JAX-M Client? Is it possible or not?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

SOAP envelopes can be modeled as XML documents (document/literal) or as XML-RPC methods (RPC/encoded). Microsoft's .NET platform leans towards the document/literal model and JAXM/SAAJ targets an XML-messaging model, so the two are a fairly good match.

.NET extends the standard set of SOAP headers to include its own set and .NET only supports Direct Internet Message Encapsulation (DIME) attachments, so these two issues must be taken into account when processing .NET SOAP messages.

Apache Axis for Java supports document/literal encoding and uses Apache's Formatting Objects Processor (FOP) to support different output formats, including DIME. These features make Axis a powerful framework for supporting .NET and Java-generated SOAP messages.

This was first published in September 2003

Back to top