Hi all, Following the is the high level design of the RM-Inbound-Endpoint that I'm developing for the WSO2 ESB. This is to be used in a scenario where the client supports RM, but the back-end service does not. RM-IE Overview <https://docs.google.com/a/wso2.com/drawings/d/1WrVsRqtzG_fKHvyt_v3YAovgvKaLoVGvlLm55qlmXbg/edit?usp=drive_web> *Operation*
- Configure the inbound endpoint in synapse.xml - Start the ESB and it will listen for the http port configured in the inbound configuration. *Request Path * - An endpoint that supports RM is created using a dummy service class - An Invoker intercepts and suspends requests that come to the endpoint - InboundSourceRequest objects are created for each request message received. - Those objects are sent to a ServerWorker in order create Synapse Message Contexts out of HttpRequests and to be injected to the insequence specified by the user. * Response Path* - The responses are injected to the out sequence specified by the user - The received responses are intercepted at the Axis2Sender - The response is set in its respective request message that was suspended earlier. - The suspended request is resumed. Thanks. Sandamal Weerasinghe | Software Engineer | WSO2 Lanka (Pvt) Ltd
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
