Java API for XML Messaging
Also, Java API for XML Messaging has several advantages over Remote Procedure Call such as the following:
- One-way (asynchronous) messaging
- Routing of a message to more than one party
- Reliable messaging with features such as guaranteed delivery
The complete JAXM API comes with two packages:
- javax.xml.soap: This package contains the API for creating and populating a SOAP message.
- javax.xml.messaging: This package allows one to send one-way messages via a messaging provider.
Messages in JAXM are XML messages that follow the prescribed SOAP format and standards. There are two main types of SOAP messages: those that have attachments and those that do not. For example, if you want your message to contain an image, you must send an attachment with the message. The SAAJ API provides the AttachmentPart class for attachments in SOAP messages.
A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination. The JAXM API provides the class and interface to represent two kinds of connections:
- javax.xml.soap.SOAPConnection—a connection from the sender directly to the receiver (a point-to-point connection)
- javax.xml.messaging.ProviderConnection—a connection to a messaging provider
A SOAPConnection is a point-to-point connection for sending messages directly to a remote party. A SOAPConnection object, which represents a point-to-point connection, is simple to create and use. You do not have to do any configuration to use a SOAPConnection object because it does not need to run in a servlet container (like Tomcat) or in a J2EE server. It is the only way for a client to have a connection without a service provider.
A ProviderConnection object represents a connection to a messaging provider. (The next section explains more about messaging providers.) When you send a message via a ProviderConnection object, the message goes to the messaging provider. The messaging provider forwards the message, following the message's routing instructions, until the message gets to the ultimate recipient's messaging provider, which in turn forwards the message to the ultimate recipient.
A messaging provider keeps track of messages and routes them to the correct destination or destinations. It is a service that handles the transmission and routing of messages.
When to use a Messaging Provider
A JAXM client may or may not use a messaging provider. Generally, you do not need a messaging provider if you just want to be a consumer of Web services. Some limitations of not using a messaging provider are the following:
The client can send only request-response messages The client can act in the client role only
Some advantages to not using a messaging provider are the following:
- The application can be written using the J2SE platform
- The application is not required to be deployed in a servlet container or a J2EE container
- No configuration is required
- JSR 67: Java(TM) APIs for XML Messaging
- Java API for XML Messaging (JAXM) Specification 1.1
- SOAP with Attachments API for Java (SAAJ) Specification 1.3
- javax.xml.messaging - this package is specified in the JAXM 1.1 specification
- javax.xml.soap - this package is specified in the SAAJ 1.3 specification
- Overview of JAXM
- Hello World Example for JAXM