Class XMPPSender

    • Constructor Detail

      • XMPPSender

        public XMPPSender()
    • Method Detail

      • cleanup

        public void cleanup​(MessageContext msgContext)
                     throws AxisFault
        Description copied from interface: TransportSender
        Release resources associated with a given message context. This method is called after processing the response of an invocation of a synchronous out-in operation to allow the transport to release any resources allocated during that invocation.

        This method is mainly useful for connection oriented transports that return from Handler.invoke(MessageContext) before the entire response is available. A transport of this type will construct an InputStream object and set it as the MessageContext.TRANSPORT_IN property on the OperationContext). In order for this to work, the connection must remain open until the response has been processed. This method is then used to release the connection explicitly.

        Specified by:
        cleanup in interface TransportSender
        Throws:
        AxisFault
      • init

        public void init​(ConfigurationContext confContext,
                         TransportOutDescription transportOut)
                  throws AxisFault
        Initialize the transport sender by reading pre-defined connection factories for outgoing messages. These will create sessions (one per each destination dealt with) to be used when messages are being sent.
        Specified by:
        init in interface TransportSender
        Parameters:
        confContext - the configuration context
        transportOut - the transport sender definition from axis2.xml
        Throws:
        AxisFault - on error
      • invoke

        public Handler.InvocationResponse invoke​(MessageContext msgContext)
                                          throws AxisFault
        Description copied from interface: Handler
        This method will be called on each registered handler when a message needs to be processed. If the message processing is paused by the handler, then this method will be called again for the handler that paused the processing once it is resumed.

        This method may be called concurrently from multiple threads.

        Handlers that want to determine the type of message that is to be processed (e.g. response vs request, inbound vs. outbound, etc.) can retrieve that information from the MessageContext via MessageContext.getFLOW() and MessageContext.getAxisOperation().getMessageExchangePattern() APIs.

        Specified by:
        invoke in interface Handler
        Parameters:
        msgContext - the MessageContext to process with this Handler.
        Returns:
        An InvocationResponse that indicates what the next step in the message processing should be.
        Throws:
        AxisFault - if the handler encounters an error
      • processChatMessage

        public static void processChatMessage​(MessageContext msgCtx)
                                       throws AxisFault
        Process message requests that came in through chat clients
        Parameters:
        msgCtx -
        Throws:
        AxisFault