Last week, I have checked in support for deploying servicemix-http component inq web app. You just have to use the servlet org.apache.servicemix.http.HttpManagedServlet with a spring based web application with a configuration like the following one: http://svn.apache.org/viewvc/incubator/servicemix/trunk/servicemix-http/src/test/resources/org/apache/servicemix/http/spring-web.xml?revision=418086&view=markup
Cheers, Guillaume Nodet On 7/2/06, Eric Zhao <[EMAIL PROTECTED]> wrote:
Hi there, I am new to servicemix. I want to use servicemix-http and servicemix-jsr181 to expose a web service. I need to deploy it to Tomcat. The problem is it seems SM-http always uses Jetty. Is there a way to make it work with Tomcat? A related question, i think i can use HttpInOutBinding + xFireBinding to achieve the same, but it seems that this lightweight component does not expose the WSDL? That is, you can't access the wsdl from say, ../service?wsdl. Is this true? If so, it's hard for the client applications to call the web service. So this approach is not really relevant? In general, can someone comment on the best approach to expose a web service in SM, in a embdded (in web app), lightweight way, with WSDL support? Thanks! Eric -- View this message in context: http://www.nabble.com/use-servicemix-http-in-Tomcat-tf1879425.html#a5137886 Sent from the ServiceMix - User forum at Nabble.com.
