|OnewayListener||A marker interface for components (for example, servlets) that are intended to be consumers of one-way (asynchronous) JAXM messages.||code | html|
|ProviderConnection||A client's active connection to its messaging provider.||code | html|
|ProviderMetaData||Information about the messaging provider to which a client has a connection.||code | html|
|ReqRespListener||A marker interface for components that are intended to be consumers of request-response messages.||code | html|
|JAXMServlet||The superclass for components that live in a servlet container that receives JAXM messages.||code | html|
|ProviderConnectionFactory||A factory for creating connections to a particular messaging provider.||code | html|
|Endpoint||An opaque representation of an application endpoint.||code | html|
|FactoryFinder||code | html|
|JAXMException||An exception that signals that a JAXM exception has occurred.||code | html|
|URLEndpoint||A special case of the
||code | html|
A client using JavaTM API for XML Messaging technology ("JAXM client") makes its connections to a messaging provider, which means that all messages it sends or receives go through the provider. The messaging provider is responsible for the delivery of messages, performing many functions behind the scenes. With a messaging provider, it is possible to send a message to multiple destinations, and a messaging provider can be configured to do the following:
The API in the
javax.xml.messaging package makes it
possible to do one-way messaging.
One-way messaging allows the client to send a message
and immediately go on to other work because the
response, if there is one, will be sent as a separate operation at
some time in the future.
javax.xml.messaging package must always work in conjunction
javax.xml.soap package, which provides the
API for constructing SOAP messages and retreiving their content.
javax.xml.soap package is
defined in the SOAP with Attachments API for
JavaTM (SAAJ) 1.1 specification.)
javax.xml.messagingpackage and explains how its classes and interfaces work.