Hi Simon and Ant, We have tried to put a port to ws.binding to reference an existing WSDL, which had the correct port in, but without success. Also, we did another test and tried to specify the uri attribute to binding.ws, but it didn't work either.
I will now try to reconfigure websphere to port 8080 and see if it works. Ant are you saying that the Websphere problem would get resolved if the hardcoded port 8085 is removed from Tuscany code? Thanks, Radim On 9/13/07, ant elder <[EMAIL PROTECTED]> wrote: > On 9/13/07, Simon Nash <[EMAIL PROTECTED]> wrote: > > > > See inline. > > > > Simon > > > > Radim Kolarik wrote: > > > > > Oh, sorry about the stack trace, it only occurs with older version of > > > Tuscany when TuscanyServlet is used instead of filters. > > > > > > I am now using Tuscany snapshot from the Maven repository dated 4th > > > September, with filters set up in web.xml, but still no luck on > > > Websphere. There is now no warning or exception in the log, but the > > > service is not being picked up. It is being picked up in Tomcat. > > > > > > Do you have any ideas? > > > > > > Thanks, > > > Radim > > > > > > On 9/13/07, Radim Kolarik <[EMAIL PROTECTED]> wrote: > > > > > >>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. > > >> > > I think this might be connected with the port number. If your > > .composite file just uses the <binding.ws/> element with dynamic WSDL > > generation and no "uri" attribute, then Tuscany will construct a default > > URI. There's a hardcoded port number of 8085 in the Axis2ServiceProvider > > code, but I think in a webapp environment Tuscany would look for the > > webapp server's configured port or fall back to 8080 if it doesn't know > > what this is. (I'm not 100% sure of the details of how this works.) > > > That Axis2ServiceProvider has port 8085 hard coded is a bug. > Axis2ServiceProvider should only be registering the servlet with an explicit > port if <binding.ws> specifies an explicit port. If <binding.ws> doesn't > specify the port then its down to the ServletHost impl to use the default > one, and thats what our WebAppServletHost will do. If we remove the > hardcoded port 8085 in Axis2ServiceProvider this all works fine. The > Tuscany-Geronimo integration also has this problem which is why I was trying > to remove the hard coded port :) > > ...ant > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
