Good stuff. I'll see if this resolves the issues and let you know. I'm surprised that this ability isn't implemented because multiple service deployments are not uncommon (I think). Of course, I can always deploy each of the 30 + services individually and perhaps that's a cleaner approach.
Glen Mazza-2 wrote: > > I haven't done that before, but I suspect that configuration could be > done in your WAR file's web.xml[1]. Might multiple <servlet-mapping/> > elements to your two web service's SEI implementation classes solve the > problem? Let us know if that works. > > HTH, > Glen > > [1] http://www.jroller.com/gmazza/date/20071019#step7 > > > Am Mittwoch, den 06.02.2008, 14:22 -0800 schrieb JavaRunner: >> I must be missing something very simple. I've deployed a project with >> multiple service classes. I had assumed that I would just add the >> service >> definition to the cxf-servlet.xml file like this: >> >> <simple:server id="serviceA" serviceClass="com.foo.service.Accounts" >> address="/accounts"> >> <simple:serviceBean> >> <bean class="com.foo.service.AccountsImpl" /> >> </simple:serviceBean> >> </simple:server> >> <simple:server id="serviceB" serviceClass="com.foo.service.Pricing" >> address="/pricing"> >> <simple:serviceBean> >> <bean class="com.foo.service.PricingImpl" /> >> </simple:serviceBean> >> </simple:server> >> >> When deployed (to Tomcat) only ServiceA is visible/available. >> Obviously there's another way. What am missing? > > > -- View this message in context: http://www.nabble.com/Multiple-Services-Question-tp15315098p15334972.html Sent from the cxf-user mailing list archive at Nabble.com.
