Ok, I'm trying to create a simple mediator that simply route an HTTP request to an endpoint, returning the unchanged response. This is an example of main sequence.
<syn:sequence xmlns:syn="http://ws.apache.org/ns/synapse"; name="main" trace="enable"> <syn:in> <syn:log level="full" /> <syn:filter xmlns:ns2="http://org.apache.synapse/xsd"; xmlns:ns="http://org.apache.synapse/xsd"; source="get-property('To')" regex="/testMediator.*"> <syn:then> <syn:send> <syn:endpoint> <syn:address uri="http://163.162.24.65:9763/myTestUrl"; /> </syn:endpoint> </syn:send> </syn:then> <syn:else /> </syn:filter> </syn:in> <syn:out> <syn:log level="full" /> <syn:send /> </syn:out> </syn:sequence> When I send the request to http://localhost:8280/testMediator, the log says that the request is correctly processed by the mediator, but it is sent to http://163.162.24.65:9763/myTestUrl/testMediator?null instead of http://163.162.24.65:9763/myTestUrl (as specified in the endpoint) If the regex is matched, why does it send the packet to the wrong concatenation, and not to the endpoint that I've specified? Also, there is a strange second concatenation with null. Any idea? Thanks ________________________________________ Da: [email protected] [[email protected]] per conto di Paul Fremantle [[email protected]] Inviato: lunedì 15 febbraio 2010 10.47 A: carbon-dev Oggetto: Re: [Carbon-dev] Using ESB mediator for non-SOAP protocols Roberto Our internal data model is based on SOAP. However, that does not mean you cannot mediate non-SOAP messages. We simply wrap the message in a "virtual SOAP" message internally to make sure that we have space for headers, etc. However, when you send the message on, it can still be a pure REST message. I hope this makes sense. Paul On 15 February 2010 09:41, Cappa Roberto <[email protected]<mailto:[email protected]>> wrote: Hi, I need to mediate via ESB requests that are not SOAP messages. I also tried to mediate a REST request, but I saw that the request was converted in a SOAP message before it can be mediated or forwarded by ESB sequences. Is there the possibility to simply forward messages that are not SOAP? For example simple HTTP requests whitout altering or transforming the packet, or JMS non-SOAP messages, or Hessian, or others... Thanks in advance _______________________________________________ Carbon-dev mailing list [email protected]<mailto:[email protected]> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse Office: +44 844 484 8143 Cell: +44 798 447 4618 blog: http://pzf.fremantle.org twitter.com/pzfreo<http://twitter.com/pzfreo> [email protected]<mailto:[email protected]> wso2.com<http://wso2.com> Lean Enterprise Middleware _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
