I've been doing work to resolve this same issue for our company. We're going
to need to deploy Servicemix in a war and use the appserver provided web
container as opposed to Jetty. My solution was to create a new
HttpSoapInOutBinding that I could point to a target component (as opposed to
a target service). This allows one instance of SpringBindingServlet to bind
to more than one service and provide wsdls for each service it's bound to.
It's not a general solution yet in that it only allows you to expose Jsr181
component endpoints, but I don't believe it would be terribly difficult to
extend it to support other target component types (e.g. jca) as well.
--
View this message in context:
http://www.nabble.com/Question-regarding-servicemix-http-t1818848.html#a5017827
Sent from the ServiceMix - User forum at Nabble.com.
