Interoperability with Other Messaging Applications A very critical feature of the Web service architecture is that the components of a Web service are often developed and hosted on heterogeneous environments. Yet they are capable of communication with each other because of the following: -
A packaging model that is independent of the transport mechanism. -
An agreement between communicating parties about the use of SOAP header structures, manifest, and so on. Both rules are adhered to by the JAXM specification to ensure that interoperability is maintained. JAXM providers implement their transport bindings in accordance with the SOAP 1.1 specification. This implies that they support SOAP 1.1 bindings for the HTTP protocol. Additionally, JAXM providers might also choose to support bindings for other networking protocols, such as SMTP, FTP, and so on. JAXM also supports the use of a higher-level industry messaging protocol based on SOAP standards, such as ebXML. This industry-specific usage of SOAP is called a profile in the JAXM specification, and JAXM supports them. Although a JAXM provider is only expected to support SOAP 1.1 and SOAP with Attachment standards, it is free to provide support for profiles. A messaging provider can support more than one profile. However, a JAXM client can use only one profile at a time. Also, the JAXM client needs to have a prior agreement with the recipient applications about the profile being used. A profile affects a SOAP message's header. However, the JAXM specification does not mandate what XML content must be put in the SOAP header, body, or attachments. Typically, a profile will specify important information such as the sender, recipient, message ID, and correlation information in the SOAP header. The correlation information identifies the request for which the current message is a response. The JAXM reference implementation includes APIs for both the ebXML and SOAP-RP profiles. You can access the Javadoc documentation for these profiles at <JWSDP_HOME>/docs/jaxm/profiles/index.html. Therefore, a JAXM client/message provider interoperates with a non-JAXM client or service by agreeing on the SOAP transport bindings and messaging profiles. | 
Print 
E-Mail 
Add Note 
Add Bookmark
