org.apache.axis2.engine
Class AxisEngine

java.lang.Object
  extended byorg.apache.axis2.engine.AxisEngine

public class AxisEngine
extends java.lang.Object

There is one engine for the Server and the Client. the send() and receive() Methods are the basic operations the Sync, Async messageing are build on top.


Constructor Summary
AxisEngine(ConfigurationContext engineContext)
          Constructor AxisEngine
 
Method Summary
 MessageContext createFaultMessageContext(MessageContext processingContext, java.lang.Throwable e)
          Deprecated. (post 1.1 branch)
 Handler.InvocationResponse invoke(MessageContext msgContext, boolean inbound, boolean resuming)
          Take the execution chain from the msgContext , and then take the current Index and invoke all the phases in the arraylist if the msgContext is pauesd then the execution will be breaked
 Handler.InvocationResponse receive(MessageContext msgContext)
          This methods represents the inflow of the Axis, this could be either at the server side or the client side.
 Handler.InvocationResponse receiveFault(MessageContext msgContext)
          This is invoked when a SOAP Fault is received from a Other SOAP Node Receives a SOAP fault from another SOAP node.
 Handler.InvocationResponse resume(MessageContext msgctx)
          Resume processing of a message.
 Handler.InvocationResponse resumeReceive(MessageContext msgContext)
          If the msgConetext is puased and try to invoke then first invoke the phase list and after the message receiver
 Handler.InvocationResponse resumeSend(MessageContext msgContext)
          To resume the invocation at the send path , this is neened since it is require to call TransportSender at the end
 void send(MessageContext msgContext)
          This methods represents the outflow of the Axis, this could be either at the server side or the client side.
 void sendFault(MessageContext msgContext)
          Sends the SOAP Fault to another SOAP node.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

AxisEngine

public AxisEngine(ConfigurationContext engineContext)
Constructor AxisEngine

Method Detail

createFaultMessageContext

public MessageContext createFaultMessageContext(MessageContext processingContext,
                                                java.lang.Throwable e)
                                         throws AxisFault
Deprecated. (post 1.1 branch)

This method is called to handle any error that occurs at inflow or outflow. But if the method is called twice, it implies that sending the error handling has failed, in which case the method logs the error and exists.

Throws:
AxisFault

receive

public Handler.InvocationResponse receive(MessageContext msgContext)
                                   throws AxisFault
This methods represents the inflow of the Axis, this could be either at the server side or the client side. Here the ExecutionChain is created using the Phases. The Handlers at the each Phases is ordered in deployment time by the deployment module

Throws:
AxisFault
See Also:
MessageContext, Phase, Handler

invoke

public Handler.InvocationResponse invoke(MessageContext msgContext,
                                         boolean inbound,
                                         boolean resuming)
                                  throws AxisFault
Take the execution chain from the msgContext , and then take the current Index and invoke all the phases in the arraylist if the msgContext is pauesd then the execution will be breaked

Parameters:
msgContext -
Returns:
An InvocationResponse that indicates what the next step in the message processing should be.
Throws:
AxisFault

resumeReceive

public Handler.InvocationResponse resumeReceive(MessageContext msgContext)
                                         throws AxisFault
If the msgConetext is puased and try to invoke then first invoke the phase list and after the message receiver

Parameters:
msgContext -
Returns:
An InvocationResponse allowing the invoker to perhaps determine whether or not the message processing will ever succeed.
Throws:
AxisFault

resumeSend

public Handler.InvocationResponse resumeSend(MessageContext msgContext)
                                      throws AxisFault
To resume the invocation at the send path , this is neened since it is require to call TransportSender at the end

Parameters:
msgContext -
Returns:
An InvocationResponse allowing the invoker to perhaps determine whether or not the message processing will ever succeed.
Throws:
AxisFault

receiveFault

public Handler.InvocationResponse receiveFault(MessageContext msgContext)
                                        throws AxisFault
This is invoked when a SOAP Fault is received from a Other SOAP Node Receives a SOAP fault from another SOAP node.

Parameters:
msgContext -
Throws:
AxisFault

resume

public Handler.InvocationResponse resume(MessageContext msgctx)
                                  throws AxisFault
Resume processing of a message.

Parameters:
msgctx -
Returns:
An InvocationResponse allowing the invoker to perhaps determine whether or not the message processing will ever succeed.
Throws:
AxisFault

send

public void send(MessageContext msgContext)
          throws AxisFault
This methods represents the outflow of the Axis, this could be either at the server side or the client side. Here the ExecutionChain is created using the Phases. The Handlers at the each Phases is ordered in deployment time by the deployment module

Parameters:
msgContext -
Throws:
AxisFault
See Also:
MessageContext, Phase, Handler

sendFault

public void sendFault(MessageContext msgContext)
               throws AxisFault
Sends the SOAP Fault to another SOAP node.

Parameters:
msgContext -
Throws:
AxisFault


Copyright © 2004-2007 Apache Software Foundation. All Rights Reserved.