Save This Page
Home » axis2-1.5-src » org.apache » axis2 » engine » [javadoc | source]
org.apache.axis2.engine
public class: AxisEngine [javadoc | source]
java.lang.Object
   org.apache.axis2.engine.AxisEngine
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.
Method from org.apache.axis2.engine.AxisEngine Summary:
createFaultMessageContext,   receive,   resume,   resumeReceive,   resumeSend,   resumeSendFault,   send,   sendFault
Methods from java.lang.Object:
equals,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.apache.axis2.engine.AxisEngine Detail:
 public static MessageContext createFaultMessageContext(MessageContext processingContext,
    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.
 public static 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
 public static InvocationResponse resume(MessageContext msgctx) throws AxisFault 
    Resume processing of a message.
 public static 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
 public static 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
 public static  void resumeSendFault(MessageContext msgContext) throws AxisFault 
    here we assume that it is resume from an operation level handler
 public static  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
 public static  void sendFault(MessageContext msgContext) throws AxisFault 
    Sends the SOAP Fault to another SOAP node.