geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Sun (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2789) allow users to specify something other than services in url-pattern in axis2 jax-ws wars
Date Wed, 31 Jan 2007 22:02:05 GMT


Lin Sun updated GERONIMO-2789:

    Attachment: G2789.patch

> allow users to specify something other than services in url-pattern in axis2 jax-ws wars
> ----------------------------------------------------------------------------------------
>                 Key: GERONIMO-2789
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: webservices
>    Affects Versions: 2.0-M2
>         Environment: winxp + sun jdk 1.5
>            Reporter: Lin Sun
>             Fix For: 2.0-M2
>         Attachments: G2789.patch
> In jax-ws test for axis2, we had to specify /services/* as the url-pattern for the servlet:
> <servlet-mapping>
>         <servlet-name>cxfPojoServlet</servlet-name>
>         <url-pattern>/services/*</url-pattern>
> </servlet-mapping>
> This is because the axis2 configurationcontext default the servicePath to "services".
  However, that is not good for our user, which means they have to put services inside of
their url-pattern.   The fix is to use the configurationContext.setServicePath method to override
the default 'services' value.  This looks okay to me as we are building one configurationcontext
and one axisservice per endpointClass.
> To do this, I grab the url-pattern from servlet-mapping specified in web.xml and set
url-pattern for the user when none is specified for the servlet/Implclass.   I've tested the
cases where a user specified /servlet/* or /servlet/lin/* as the url-pattern and it both works
fine when running the jax-ws test with the RPCMessageReceiver code (before 2776 is checked
> I've commented code where it will throws exception when the url-pattern contains a star
as that issue hasn't been resolved yet.
> The code built fine with the latest change in trunk but  I haven't been able to get the
jax-ws  war file deployed yet (issues not related to this patch).

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

View raw message