Hi Sebastian, I received the latest code from ant and I can confirm that the service generates the WSDL file now. The <binding.ws/> element doesn't even need uri attribute, it works without any attributes!
However, there is still some problem, the generated WSDL contains Error 404: SRVE0190E: File not found: /ComponentName at it's end, right after the </wsdl:definitions>. I have created a JIRA for this: https://issues.apache.org/jira/browse/TUSCANY-1702. Are you seeing the same problem? Best regards, Radim On 9/14/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > Radim Kolarik wrote: > > Hi Yang, > > > > unfortunatelly, that didn't help either. > > > > Thanks, > > Radim > > > > On 9/14/07, Yang Lei <[EMAIL PROTECTED]> wrote: > > > >> Try remove the contextRoot and see if you can get the values. > >> > >> Yang > >> > >> > >> On 9/13/07, Radim Kolarik <[EMAIL PROTECTED]> wrote: > >> > >>> Hi Simon, > >>> > >>> please ignore the --, it was just added to thread by accident. The > >>> file I work with is a valid XML file. > >>> > >>> The URI even gets picked up from the .composite file during > >>> inicialization, I get the addServletMapping: > >>> /contextroot/ExampleComponent/ExampleService in the log file. > >>> > >>> But I do not see any initContextPath: in the log, maybe that could be > >>> signaling the problem? > >>> > >>> Thanks, > >>> Radim > >>> > >>> > Hi Radim, > > I did some investigation, here's what I found: > > - If you're not seeing initContextPath but seeing addServletMapping in > the log, that's probably because you're using a level of code prior to > the addition of initContextPath, I'm guessing that you're using the last > published snapshot? Anyway, don't worry about it, that's not the issue. > > - The issue you've run into is caused by different behavior of > HttpServletRequest.getServletPath() between WebSphere and Tomcat/Jetty > when invoked from a ServletFilter. In your example, on Tomcat/Jetty > getServletPath() will return "/ExampleComponent", on WebSphere > getServletPath() returns "" and "/ExampleComponent" can be found in > request.getPathInfo() instead. I am not sure which one is correct, > WebSphere or Tomcat/Jetty, but for now I've changed TuscanyServletFilter > to tolerate both. > > - If your component has a single service, it will be available at > http://localhost:9080/contextRoot/ExampleComponent instead of > http://localhost:9080/contextRoot/ExampleComponent/ExampleService. I > think that this is consistent with what the SCA spec 1.0 says about URIs > of deployed bindings. > > - You should have xalan-2.7.0.jar in your WAR WEB-INF/lib and make sure > that you don't have any servlet-api JAR in there. > > - Finally, in the WebSphere admin console, you should configure your > Webapp with Webapp Class Loader order = "Classes loaded with application > class loader first" and WAR ClassLoader policy = "Single class loader > for application". > > With this configuration, and the few fixes I just committed in SVN > revision 575610, I am able to run the calculator-webapp (a JSP calling > the calculator component locally) and calculator-webapp-ws (exercising > both a reference a service with WS bindings) samples on WebSphere 6.1. > > Hope this helps... > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > 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]
