Package org.apache.axis2.engine
Class AxisEngine
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.
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic Handler.InvocationResponsereceive(MessageContext msgContext) This methods represents the inflow of the Axis, this could be either at the server side or the client side.static Handler.InvocationResponseresume(MessageContext msgctx) Resume processing of a message.static Handler.InvocationResponseresumeReceive(MessageContext msgContext) If the msgConetext is puased and try to invoke then first invoke the phase list and after the message receiverstatic Handler.InvocationResponseresumeSend(MessageContext msgContext) To resume the invocation at the send path , this is neened since it is require to call TransportSender at the endstatic voidresumeSendFault(MessageContext msgContext) here we assume that it is resume from an operation level handlerstatic voidsend(MessageContext msgContext) This methods represents the outflow of the Axis, this could be either at the server side or the client side.static voidsendFault(MessageContext msgContext) Sends the SOAP Fault to another SOAP node.
-
Constructor Details
-
AxisEngine
public AxisEngine()
-
-
Method Details
-
receive
This methods represents the inflow of the Axis, this could be either at the server side or the client side. Here theExecutionChainis created using the Phases. The Handlers at the each Phases is ordered in deployment time by the deployment module- Throws:
AxisFault- See Also:
-
resumeReceive
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
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
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
This methods represents the outflow of the Axis, this could be either at the server side or the client side. Here theExecutionChainis 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
Sends the SOAP Fault to another SOAP node.- Parameters:
msgContext-- Throws:
AxisFault
-
resumeSendFault
here we assume that it is resume from an operation level handler- Parameters:
msgContext-- Throws:
AxisFault
-