L.S.,
First of all, I have changed
http://cwiki.apache.org/confluence/display/SM/Creating+a+protocol+bridge.
Could you check if all necessary changes have been done? This page will
get replicated to the main site after a while...
For your second use case: if you do not need any transformations on the
message content, you can create a service assembly with two service units:
- one SU based on servicemix-jms, defining the JMS consumer endpoint to
read messages from a JMS queue (cfr.
http://incubator.apache.org/servicemix/servicemix-jms.html for
configuration options)
- the other SU based on servicemix-http, defining the HTTP provider
endpoint which points to your webservice (cfr.
http://incubator.apache.org/servicemix/servicemix-http.html for
configuration options)
Beware that the service/endpoint name of you HTTP provider endpoint
should match the names defined in your webservice's WSDL. You can
either use the same service/endpoint name on your JMS endpoint or use
the targetService/targetEndpoint attributes to do the routing.
Regards,
Gert
gauravsonline wrote:
HI,
Thanks for your help. Actualy just now I resolved the problem.
The problem was in the xslt-su. The archtyope by default generates the
servicemix.xml file and in the example code its xbean.xml file. So just
renaming the file from servicemix.xml to xbean.xml. The saxon dependency was
ok.
Now the next step is to read the messages from the queue and call a web
service. Could you please help??
Also I would like to request the moderator if they could update this thing
at :
http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html
http://incubator.apache.org/servicemix/creating-a-protocol-bridge.html
in the "XSLT SU" section, as this has costed me two days to resolve.
Thanks all for your help!
