[ 
https://issues.apache.org/jira/browse/TUSCANY-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525027
 ] 

ant elder commented on TUSCANY-1654:
------------------------------------

Ok i've got the geronimo-tuscany integration up and running and have been able 
to debug through this, the problem is an issue with the way the context path is 
getting handled in the geronimo-tuscany code.

When running in the Tuscany-Geronimo integration calling getContextPath on the 
HttpServletRequest passed in on service(HttpServletRequest, 
HttpServletResponse) gives different results than when Tuscany is running as a 
webapp in Tomcat or in the Tuscany Jetty and Tomcat standalone hosts.

In Geronimo getContextPath is returning the first part of the url path whereas 
Tuscany may be using that as part of the service name. So if you deploy a 
service using <binidng.ws uri="http://localhost:8080/hello/HelloService"/> then 
in the Geronimo/Tuscany integration getContextPath returns "/hello" whereas in 
the other environments "hello" is not included.

This looks to me like a problem in the geronimo-tuscany integration code, eg in 
GeronimoServletHost.addServletMapping. 

But its also a design issue - what should the context path be? In Geronimo you 
can't deploy an SCA service with a context path of "/" as thats used by J2EE 
apps, so they MUST have another path (i'm guessing thats why "hello/" is added 
to the URL in the sample above).

In the Tuscany standalone hosts a context path of "/" works, with Tuscany 
running as a webapp or in the Tuscany webapp distro it does not and the webapp 
name is used as the context path. Maybe the  Geronimo-Tuscany integration needs 
to do that, eg as in the webapp distro use something like "tuscany/" or "sca/" 
as a fixed context path for all services.






> Problem getting wsdl for service ws binding
> -------------------------------------------
>
>                 Key: TUSCANY-1654
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1654
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-0.99
>         Environment: Tuscany SCA 0.99 runtime used in "Tuscany plugin for 
> Geronimo 2.0.1 Tomcat" distro.
>            Reporter: Vamsavardhana Reddy
>             Fix For: Java-SCA-Next
>
>         Attachments: TUSCANY-1654.patch
>
>
> I have encountered this problem with getting wsdl for service ws binding with 
> helloworld webservice sample deployed in Geronimo using Tuscany plugin for 
> Geronimo.  Creating this JIRA to keep track of any observations and progress 
> on this problem.  I suspect the problem is introduced in rev 569074.  Part of 
> the discussion on tuscany-dev is available at  
> http://www.mail-archive.com/[email protected]/msg22334.html.
> Problem:  After deploying helloworld webservice sample with ws binding URI 
> http://localhost:8080/hello/HelloWorldService, accessing 
> "http://localhost:8080/hello/HelloWorldService?wsdl"; throws 
> StringIndexOutOfBoundsException.
> Observations:
> 1.  Though accessing http://localhost:8080/hello/HelloWorldService?wsdl 
> results in an error, the service is still available at 
> http://localhost:8080/hello/HelloWorldService
> 2.  If a URI http://localhost:8080/HelloWorldService is used, then 
> http://localhost:8080/HelloWorldService?wsdl does not result in any errors 
> i.e. when the context-root is "/".
> 3.  The HelloWorldService sample under samples runs fine with either URI's in 
> standalone tuscany runtime.  This is because "/" is used as the context-root 
> in both the cases.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to