Yes, that's what I've done. What I see in the logs is that both endpoints get deployed, the publish addresses are both logged, but after "All endpoints have been deployed and components initialized. Registering service assembly." I see "Changing SA state to Stopped" followed by a "Registering endpoint" but only for the one with the ENDPOINT_NAME=FooImplPort not the ENDPOINT_NAME=soap. The second endpoint never gets restarted.
Dan On Oct 29, 2010, at 3:17 PM, Jean-Baptiste Onofré wrote: > Hi Dan, > > You can gather cxfbc and cxfse in the same xbean.xml (and so in the same > bundle). > In fact, now you can gather all components in the same xbean.xml. After you > can package this xbean.xml in a bundle or directly drop into the deploy > folder. > > To "expose" the component endpoints as an OSGi service, simply add: > > <bean class="org.apache.servicemix.commons.osgi.EndpointExporter"/> > > Take a look on: > http://servicemix.apache.org/SMX4/creating-an-osgi-bundle-for-deploying-jbi-endpoints.html > http://servicemix.apache.org/SMX4NMR/3-deploying-jbi-components-without-the-jbi-packaging.html > http://servicemix.apache.org/file-to-xmpp-bridge.html > > Regards > JB > > On 10/29/2010 05:54 PM, Dan Powell wrote: >> Is it possible to combine the cxfbc:consumer and cxfse:endpoint into a >> single bundle? t seems the second endpoint to start replaces the first. >> When I list both in the Spring beans.xml with the cxfbc:consumer first, I >> see the publish address for both endpoints (one as http://0.0.0.0:9090/foo >> and the other as jbi://ID-10-122-125-215-12bf890562c-2-0) logged to >> data/servicemix.log, but the HTTP port is not listening. Also if I reverse >> the order and declare the cxfbc:consumer after the cxfse:endpoint, the HTTP >> port is listening and serves the ?wsdl request but invocations of the >> service result in "Could not dispatch exchange. No matching endpoints." >> >> Thanks! >> >> Dan
smime.p7s
Description: S/MIME cryptographic signature
