The Java API for XML Messaging (JAXM) enables distributed software applications to communicate using XML (and SOAP). JAXM supports both asynchronous and synchronous messaging.
The Java API for XML Messaging (JAXM) enables developers to use XML messaging using the Java platform. Developers can create and send XML messages over the internet using the JAXM API.[1]
The following figure presents a conceptual relationship between JAXM and other architectural elements required in web-based, business-to-business 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
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
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.[3]
Connections
A connection is required to send and receive all SOAP messages. The connection can go to a messaging provider or a particular destination.[4]
The JAXM API provides the class and interface to represent two kinds of connections:
A SOAPConnection is a point-to-point connection for sending messages directly to a remote party.[5] 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.[6]
Provider Connection
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.[7]
Messaging Providers
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.[8]
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
