[
https://issues.apache.org/jira/browse/TUSCANY-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1481.
---------------------------------------------
Resolution: Won't Fix
When we package services in a webapp, I think that we have to accept that part
of their URIs will be ignored as host, port, and context root are fixed by the
Web container and cannot be controlled anymore by the SCA runtime embedded in
that Web container.
This is not necessarily an issue, there are other examples where part of the
service/binding URI used to publish a service is ignored or becomes irrelevant:
- "localhost" for example is ignored in the standalone runtime, assuming that a
service is always running on localhost, in this case the host name (or names)
cannot be controlled by the SCA runtime as it is fixed by the machine on which
it runs and its network configuration
- the complete URI can also become irrelevant in many other cases, in presence
of virtual hosting, proxies, redirections, or URI aliasing, all of which are
external to the SCA runtime.
> 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
> Fix For: Java-SCA-1.0
>
>
> 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]
