This RI tries to provide an application programming model for both servlet-based b-to-b applications and standalone b-to-b applications.
The rest of this document briefly describes what is in this release.
Point-to-point SOAP Communication
A client can send messages directly to the ultimate recipient using a
SOAPConnection object. This type of connection,
called a point-to-point connection, connects
the client to the intended recipient rather than to a messaging provider.
Therefore, when the application sends a message, the message goes directly
to the intended recipient. This kind of SOAP message exchange uses the APIs
in the javax.xml.soap package. SOAPConnection
(and
its related classes) is a pure library implementation that lets you send
SOAP messages directly to a remote party. This model is simple to get started
but has limited possibilities for reliability and message delivery guarantees.
For instance, the point-to-point message exchange model relies largely on
the reliability of the underlying transport for delivering a message.
Remote Provider
A remote provider, also called a messaging provider, is akin to a
messaging server. The messaging provider takes a
message sent by an application and holds on to it until the message has been
successfully delivered. The application itself may be active or quiescent, but
the remote provider continues to try to deliver any messages that the application
has sent and to receive any incoming messages on the application's behalf.
When an application comes up and establishes a connection to the remote
provider, messages received by the provider for that application are delivered
to it. All messages sent through a remote provider are logged for perusal
later. APIs to work with the remote provider are in the javax.xml.messaging
package
of the JAXM API.
The JAXM provider administration tool allows users to make changes to
the provider configuration. It is expected that the main users will
be Systems Administrators, but anyone who needs to change the configuration for
the provider can use it. The login and password for the tool are set
to use the defaults of the web container. For Tomcat, we use the default
login "tomcat" and and the default password "tomcat".
Some typical ways to change the provider properties are:
samples
directory) to get you started:
This release of JAXM relies on DOM4J which is covered the is covered by the DOM4J Software License.
Please send feedback on this JAXM 1.1 release to jaxm-feedback@sun.com.