On Wed, Jan 12, 2011 at 12:48 PM, nch <underscore_...@yahoo.com> wrote: > Hi, there. > > I have developed two Axis2 web services. Both integrate with Spring > following http://axis.apache.org/axis2/java/core/docs/spring.html#a26 > Both services work correctly when deployed alone but, if both are deployed, > only > the service that was last deployed works. The previously deployed services > fail > with: > > <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";> > <soapenv:Body> > <soapenv:Fault> > <faultcode>soapenv:Server</faultcode> > <faultstring>unknown</faultstring> > <detail/> > </soapenv:Fault> > </soapenv:Body> > </soapenv:Envelope> > > My guess is that both services are using the same application context so, as > if > each time one of them is deployed it makes a refresh of the context, the > previous definitions are lost. If so, how can I have a per-service application > context? > Anyway what do you think is causing this issue? How can I solve it? > > Many thanks in advance. >
What version of axis2 are you using? Are you using the "Spring Inside an AAR" example? If so, each spring instance is entirely separate - you can use the same exact config in each AAR, each having a per-service application context. Be sure to follow all the directions carefully. Put Spring and axis2 in debug if in doubt about having two separate spring configs. Also post a stacktrace for your error. - R --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
