Java Web Services in a Nutshell

JAXM Client and Provider Configuration

Availability

Java Web Services Developer’s Pack. There is no equivalent for the J2EE 1.4 platform, since JAXM is not included.

Description

The Java API for XML Messaging (JAXM) provides a means to send and receive SOAP messages via a provider instead of using a direct connection from the sender to the receiver. The benefits of this arrangement, as discussed in Chapter 4, are:

Asynchronous operation

Clients deliver outgoing messages to their provider. The provider then has responsibility for arranging the delivery of each message to the provider local to the intended recipient. If the receiving provider is not active or not reachable, it will be necessary to retry delivery until it succeeds or a preconfigured limit is reached.

Persistence

Messages can be received for a client that is not active and stored within the provider for delivery later.

Location transparency

Whereas SAAJ applications need to know the address of the recipient of each message they send, a JAXM client can use an address token that is independent of the real address of the receiving application. The mapping from an address token to an actual address is configured in the provider, where it can be more easily changed if necessary.

In order to provide these features, two levels of configuration are required. First, the provider has to be configured with the details of the token-to-address mappings that provide location transparency for applications and with other information, such as ...