Hi Yang, thank you for your suggestions.
I am sure I use the correct root context, because I can access a JSP within the application successfully. It seems to me that the axis service is not being recognized at http://localhost:9201/contextRoot/componentName/serviceName. It is very strange, because if I deploy the same WAR to Tomcat, it works fine. We have also tried attaching a static WSDL file, again, that gets displayed fine in Tomcat, but on Websphere, we get: [9/13/07 12:36:14:309 IST] 00000035 WebApp E [Servlet Error]-[TuscanyServlet]: java.lang.StringIndexOutOfBoundsException at java.lang.String.substring(String.java:1081) at org.apache.tuscany.sca.binding.ws.axis2.TuscanyListingAgent.setContextRoot(TuscanyListingAgent.java:286) at org.apache.tuscany.sca.binding.ws.axis2.TuscanyListingAgent.processListService(TuscanyListingAgent.java:102) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.doGet(Axis2ServiceServlet.java:260) at javax.servlet.http.HttpServlet.service(HttpServlet.java:743) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.service(Axis2ServiceServlet.java:235) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at org.apache.tuscany.sca.host.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:77) at org.apache.tuscany.sca.host.webapp.TuscanyServlet.service(TuscanyServlet.java:63) at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:966) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:478) at com.ibm.ws.wswebcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:463) at com.ibm.ws.webcontainer.servlet.CacheServletWrapper.handleRequest(CacheServletWrapper.java:92) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:744) at com.ibm.ws.wswebcontainer.WebContainer.handleRequest(WebContainer.java:1425) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:92) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:465) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewInformation(HttpInboundLink.java:394) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:274) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:152) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:213) at com.ibm.io.async.AbstractAsyncFuture.fireCompletionActions(AbstractAsyncFuture.java:195) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:136) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:193) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:725) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:847) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498) Does that help? Thanks, Radim On 9/12/07, Yang Lei <[EMAIL PROTECTED]> wrote: > I assume you did all the following correct: > > - I assume the context root is correct for the war: you can use WAS > console to check the value > - I assume the port is correct. E.g. in my env, 9081 is the default > port for my war. You can also use WAS console to check the setting on > virtualHost > - I assume the componentName/ServiceName is the one you registered to > Axis 2 engine? Can you do the following to make sure Axis 2 recognize the > service? http://localhost:9201/contextRoot/componentName/serviceName if > you can then you can try > http://localhost:9201/contextRoot/componentName/serviceName/?wsdl > > Good luck. > > Yang. > > > On 9/12/07, Radim Kolarik <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > We having problems deploying our services to Websphere. We have > > resolved some WAS classloading issues as was recommended by ant elder on > > the user group, it seems that the initialization is without a problem > > now. But the URL we are trying to map, e.g. > > http://localhost:9201/contextRoot/componentName/serviceName?wsdl is not > > returning anything. > > > > Is there anybody in Tuscany team who has tried deployment to Websphere? > > The same WAR file seems to be working fine on Tomcat, however, not in > > WAS 6.1. > > > > Thanks, > > Radim > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
