org.jboss.net.axis.message.addressing.handler
Class AddressingHandler

java.lang.Object
  org.apache.axis.message.addressing.handler.AddressingHandler
      org.jboss.net.axis.message.addressing.handler.AddressingHandler

public class AddressingHandler

extends org.apache.axis.message.addressing.handler.AddressingHandler

Title:

WS-Addressing Handler

Description:

This Subclass of the org.apache.axis.message.addressing.handler.AddressingHandler will properly use the wsa:Action header to direct the incoming messages to the proper services. It also correctly fetches the client config when sending a response via the ReplyTo header. wss4j properties are also moved into the new request (server response) so encryption / signing can happen after addressing.

This handler can be placed in the global (or transport) request and response chains to handle messages with ws-addressing headers. For added security, have the ws-security (wss4j) handlers sign any ws-addressing headers that contain addresses (To, From, ReplyTo, FaultTo). This means that wss4j will have to process incoming messages BEFORE addressing, and it will have to process outgoing messages AFTER addressing.

The parameters transportPackages, and transports can be configured in the DD to allow the response objects to understand any special transports that may be in use. @see #initializeCall()

Copyright:

Copyright (c) 2004

Company:

Green River Computing Services

See Also:

Serialized Form

AddressingHandler

public AddressingHandler()

init

public void init()

configureCall

protected void configureCall(Call call,
                             MessageContext msgContext)

getService

protected Service getService(MessageContext msgContext)

setTargetService

protected void setTargetService(MessageContext msgCtx,
                                AddressingHeaders headers)
                         throws java.lang.Exception

We set the target service based upon the Action header since email addresses don't have path attributes.

Throws:

java.lang.Exception