Hey Guillaume,
I think I am getting close (and please excuse my ignorance on these
matters). What I have on the host receiving the HTTP Post is:
<sm:activationSpecs>
<sm:activationSpec>
<sm:component>
<http:component>
<http:endpoints>
<http:endpoint
service="test:MyConsumerService" endpoint="transformer"
role="consumer" soap="false"
locationURI="http://sushi:8192/dummy";
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
targetService="test:MyProviderService"/>
</http:endpoints>
</http:component>
</sm:component>
</sm:activationSpec>
<sm:activationSpec componentName="transformer"
service="foo:transformer">
<sm:component>
<bean
class="org.apache.servicemix.components.xslt.XsltComponent">
<property name="xsltResource"
value="xslt/strip-namespace.xslt"/>
</bean>
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<jms:component>
<jms:endpoints>
<jms:endpoint
service="test:MyConsumerService"
endpoint="myConsumer"
role="consumer"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
destinationStyle="queue"
jmsProviderDestinationName="queue/B"
connectionFactory="#connectionFactory"
targetService="foo:transformer"/>
<jms:endpoint
service="test:MyProviderService"
endpoint="myProvider"
role="provider"
destinationStyle="queue"
jmsProviderDestinationName="queue/A"
connectionFactory="#connectionFactory"/>
</jms:endpoints>
</jms:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
The intention is that I pass the JMS of the incoming HTTP to another maching
running SM. This other machine would then consume this XML, transform it in
some way, and pass it back. This is what I have on the other box:
<sm:activationSpecs>
<sm:activationSpec componentName="transformer" service="foo:transformer"
destinationService="test:MyConsumerService">
<sm:component>
<bean
class="org.apache.servicemix.components.xslt.XsltComponent">
<property name="xsltResource"
value="xslt/rm-request-url.xslt"/>
</bean>
</sm:component>
</sm:activationSpec>
<sm:activationSpec>
<sm:component>
<jms:component>
<jms:endpoints>
<jms:endpoint
service="test:MyConsumerService"
endpoint="myConsumer"
role="consumer"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
destinationStyle="queue"
jmsProviderDestinationName="queue/A"
connectionFactory="#connectionFactory"
targetService="foo:transformer"/>
</jms:endpoints>
</jms:component>
</sm:component>
</sm:activationSpec>
</sm:activationSpecs>
As you might imagine, what's happening is that the first box (lets call it
the host), is immediately picking up the JMS message prior to the other box
(called client) receiving and transforming it.
Do I need to setup a seperate queue to send the reply to? If so, how am I
assured that the messages are correlated?
In the future, I do hope to payback my gratitude once I get better
understanding of things through helping out with documentation etc.
Thanks,
jeff
--
View this message in context:
http://www.nabble.com/NMR-Flow-scenario-question-t1637079.html#a4454845
Sent from the ServiceMix - User forum at Nabble.com.
