You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2007/03/02 05:17:51 UTC
[jira] Resolved: (GERONIMO-2913) minor changes to
JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2
[ https://issues.apache.org/jira/browse/GERONIMO-2913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas resolved GERONIMO-2913.
----------------------------------------
Resolution: Fixed
thanks. fix is in 513612.
-- dims
> minor changes to JettyEJBWebServiceContext and TomcatEJBWebServiceContext for Axis2
> -----------------------------------------------------------------------------------
>
> Key: GERONIMO-2913
> URL: https://issues.apache.org/jira/browse/GERONIMO-2913
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: webservices
> Affects Versions: 2.0
> Environment: winxp + sun 1.5 SDK
> Reporter: Lin Sun
> Fix For: 2.0
>
> Attachments: G2913.patch
>
>
> This patch contains the following change:
> 1) In Axis2 integration code, we use request.getURI().getQuery(), however null is returned when running jaxws-ejb test as the queryString wasn't set. The patch will pass the queryString as the parameter when constructing URI.
> 2) In our Axis2 integration code, we call request.getContextPath() and it returns null from JettyEJBWebServiceContext and /JAXWS-EJB-2.0-snapshot/JAXWSBEAN from TomcatEJBWebServiceContext when running the jaxws-ejb test case. To me, the tomcat behavior is right. (See dev list on some discussion of this prob.) There seems to be a bug in Jetty in request.getContextPath() so I propose to use request.getRequestURI() instead to temply work around the prob.
> Patch has been tested and able to do a full build with it.
> Thanks, Lin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.