I believe important to mention that the invocation of RESTful WS is carried out through ‘SonicMQ Outbound Routing’; i.e., the ‘Endpoint’ in question points to ‘sonic.http::destination_name’, and I set the 'URI' required through the ‘X-HTTP-DestinationURL’ property. Again, the result from the RESTful WS is "successful", for your information, the associated HTTP method is POST, and MIME type is XML.
Please, can someone help me with this issue? Any idea about of how I would execute the ESB itinerary of end to end, without incurring in programming API, may be, setting a few properties only?...
Thanks,
César Peñalosa.
If I read the problem correctly you want to perform a REST request/reply in a step and then continue the itinerary with the result?
To do so will require and Endpoint.callout(), which synchronously waits for the response.
Unfortunately, an oob service type is only shipped with Sonic 8.0 (Dispatch service). For prior version you would want to have a (generic) custom service that performs the callout, e.g.:
XQAddress replyToAddr = envelope.getMessage().getReplyTo();
endpoint = // get REST endpoint address;
XQMessage response = endpoint.cal(envelope.getMessage(), timeout * 1000); // call and wait timout seconds
response.setReplyTo(replyToAddr); // restore orgininal replyTo
envelope.setMessage(response); // populate outgoing envelope
context.addOutgoing(envelope);
Thomas
Hi Césa,
you cannot use JMSReplyTo with the xslt wih the HeaderExtension of sonic API. I got the issue as well.
There is a Enrichment Service available at psdn, that you can use for that, try that out. I am not sure if you can use that or not. we use that and it works well for us.
I have the same scenarion, but in my case i did not use the WS, instead of we have Custom service, we are able to process the response.