THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Wiki Markup |
|---|
{snippet:id=receive|lang=xml|url=http://cvssvn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/resources/org/servicemix/components/xslt/example.xml?rev=HEAD} |
If you wish to use JCA or some other mechanism to subscribe to JMS you can use the JmsInBinding.
...
The JmsSenderComponent will send JMS messages from the input message exchange. This component uses Spring's JmsTemplate to perform the sending. The following example demonstrates a component which when invoked will send a message to a given JMS topic
| Wiki Markup |
|---|
{snippet:id=send|lang=xml|url=http://cvssvn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/resources/org/servicemix/components/xslt/example.xml?rev=HEAD} |
JMS bridges
Its a very common requirement to create a message bridge; routing messages from one messaging system to another. With ServiceMix we can connect any transport with any transport - but for now lets focus on JMS to JMS bridging. Imagine for example you wish to route messages from ActiveMQ to MQSeries, or from WebLogic JMS to ActiveMQ.
...
| Wiki Markup |
|---|
{snippet:id=pipeline|lang=xml|url=http://cvssvn.servicemix.codehaus.org/*checkout*/branches/servicemix-1.1/base/src/test/resources/org/servicemix/components/xslt/pipeline.xml?rev=HEAD} |
This example is performing an XSLT transform on the messages as well - you can perform arbitrary processing of the messages in the bridge, performing rules processing or content based routing. Obviously you could miss out the transformation step and just route the inbound message on one JMS provider to another JMS provider without any transform step.