kitplummer wrote: > > Yep. So, I take it you're not seeing it at the siteBService endpoint? > Are you sure the endpoint is activated? > Yes, a message sent to the http endpoint which has as its targetService the siteBService is generating "Could not find route" exceptions. I believe both endpoints are activated as reported by the JMX console.
kitplummer wrote: > >> Here is what I've got: >> Site A servicemix.xml defines http endpoint which has as a target service >> siteBService >> Site B servicemix.xml defines endpoint siteBService which is currently >> just >> an instance of MockServiceComponent > > Can you post your configs? > Sure thing: Site A servicemix.xml: <?xml version="1.0" encoding="UTF-8"?> <!-- SITE A--> <beans xmlns:sm="http://servicemix.apache.org/config/1.0" xmlns:foo="http://servicemix.org/demo/" xmlns:http="http://servicemix.apache.org/http/1.0"> <!-- omitted includes of property file initialization and activemq.xml import --> <bean id="jndi" class="org.apache.xbean.spring.jndi.SpringInitialContextFactory" factory-method="makeInitialContext" singleton="true"/> <!-- the JBI container --> <!-- also tried without the flowNames, defaulting to seda, same result --> <sm:container id="jbi" useMBeanServer="true" createMBeanServer="true" flowNames="jms?tcp://sitea:61616"> <sm:activationSpecs> <sm:activationSpec> <sm:component> <http:component> <http:endpoints> <http:endpoint service="foo:AsearchA" endpoint="search" role="consumer" soap="false" targetService="foo:searchProviderA" locationURI="http://sitea:8193/siteA/" defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/> <http:endpoint service="foo:AsearchB" endpoint="search" role="consumer" soap="false" targetService="foo:searchProviderB" locationURI="http://sitea:8193/siteB/" defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/> </http:endpoints> </http:component> </sm:component> </sm:activationSpec> <sm:activationSpec componentName="searchProviderA" service="foo:searchProviderA" endpoint="endpointA"> <sm:component> <bean class="org.apache.servicemix.components.util.MockServiceComponent"> <!-- as configured, the value contains the amp values, Nabble may render the actual characters --> <property name="responseXml" value="<goo>search response A</goo>"/> </bean> </sm:component> </sm:activationSpec> </sm:activationSpecs> </sm:container> </beans> Site B servicemix.xml: <?xml version="1.0" encoding="UTF-8"?> <!-- SITE B --> <beans xmlns:sm="http://servicemix.apache.org/config/1.0" xmlns:foo="http://servicemix.org/demo/" xmlns:http="http://servicemix.apache.org/http/1.0"> <!-- omitted includes of property file initialization and activemq.xml import --> <bean id="jndi" class="org.apache.xbean.spring.jndi.SpringInitialContextFactory" factory-method="makeInitialContext" singleton="true"/> <!-- the JBI container --> <!-- also tried without the flowNames, defaulting to seda, same result --> <sm:container id="jbi" useMBeanServer="true" createMBeanServer="true" flowNames="jms?tcp://siteb:61616"> <sm:activationSpecs> <sm:activationSpec> <sm:component> <http:component> <http:endpoints> <http:endpoint service="foo:BsearchA" endpoint="search" role="consumer" soap="false" targetService="foo:searchProviderA" locationURI="http://siteb:8192/siteA/" defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/> <http:endpoint service="foo:BsearchB" endpoint="search" role="consumer" soap="false" targetService="foo:searchProviderB" locationURI="http://siteb:8192/siteB/" defaultMep="http://www.w3.org/2004/08/wsdl/in-out"/> </http:endpoints> </http:component> </sm:component> </sm:activationSpec> <sm:activationSpec componentName="searchProviderB" service="foo:searchProviderB" endpoint="endpointB"> <sm:component> <bean class="org.apache.servicemix.components.util.MockServiceComponent"> <!-- as configured, the value contains the amp values, Nabble may render the actual characters --> <property name="responseXml" value="<goo>search response B</goo>"/> </bean> </sm:component> </sm:activationSpec> </sm:activationSpecs> </sm:container> </beans> -- View this message in context: http://www.nabble.com/Bus-to-Bus-Communication-tf3918026s12049.html#a11562250 Sent from the ServiceMix - User mailing list archive at Nabble.com.
