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

gengshaoguang commented on TUSCANY-1481:
----------------------------------------

Hi,
You missed something here, services are NOT registered with their full path 
info under a webapp context, but they ARE under standalone circumstance (with 
jetty or tomat runtime). So for the latest Tuscany code, this part works fine.

> TuscanyServlet looks for servlets using path info and not the whole path 
> -------------------------------------------------------------------------
>
>                 Key: TUSCANY-1481
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1481
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Web App Integration
>    Affects Versions: Java-SCA-Next
>         Environment: All
>            Reporter: Simon Laws
>
> In the TuscanyServlet service method there is code to find a registerest 
> servlet
>         String path = ((HttpServletRequest)req).getPathInfo();
>         Servlet servlet = servletHost.getServlet(path);
>         if (servlet == null) {
>                 throw new IllegalStateException("No servlet registered for 
> path: " + path);
>         }
> Currently though in the code servlets can get registered against full path 
> names, e,g, when the full path name is defined in WSDL, and hence the servlet 
> is not found. I expect it is this way as its not expecting a full path to be 
> specified. Why would it, the application is deployed into an already running 
> app server. We either need to raise an error to tell people why their 
> services can't be found or check for full path names. 
> I've dont the latter for now (see the change assoicated with this JIRA) but 
> would welcome some more thought on this issue as I expect the is a good 
> reason why it is this way. 

-- 
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