Class AxisEngine

java.lang.Object
org.apache.axis2.engine.AxisEngine

public class AxisEngine extends 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 Details

    • AxisEngine

      public AxisEngine()
  • Method Details

    • receive

      public static 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:
    • resumeReceive

      public static 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 static 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
    • resume

      public static 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 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
      Parameters:
      msgContext -
      Throws:
      AxisFault
      See Also:
    • sendFault

      public static void sendFault(MessageContext msgContext) throws AxisFault
      Sends the SOAP Fault to another SOAP node.
      Parameters:
      msgContext -
      Throws:
      AxisFault
    • resumeSendFault

      public static void resumeSendFault(MessageContext msgContext) throws AxisFault
      here we assume that it is resume from an operation level handler
      Parameters:
      msgContext -
      Throws:
      AxisFault