axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1372) Default servlet mapping for AxisServlet breaks service names
Date Wed, 29 Sep 2004 11:55:32 GMT
The following comment has been added to this issue:

     Author: Jayachandra Sekhara Rao Sunkara
    Created: Wed, 29 Sep 2004 4:55 AM
The latest attached file (second one) contains a diff done against the recent cvs repository.

Thank you
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1372
    Summary: Default servlet mapping for AxisServlet breaks service names
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Axis

   Reporter: Brian J. Sayatovic

    Created: Thu, 27 May 2004 6:41 AM
    Updated: Wed, 29 Sep 2004 4:55 AM
Environment: WebSphere 4 Test Environment under WSAD 5.1 on Windows XP.

I'm trying to set up my WAR, with context root /MyApp/MyWar, with the
default servlet being the AxisServlet from Apache AXIS 1.1.  I'm doing this on WebSphere 4.0
(right now, experimenting in WSAD 5. 1with the WAS4 test environment).

My attempt was to set the servlet mapping for AxisServlet to be just "/".  This is how WebSphere's
documentation says one should set up a default servlet mapping.  However, when I attempt to
reach my service like so...
...Axis complains that it can't find the service name "yService".  Notice the "M" is missing
from the beginning.  Interestingly, using the following URLs will work:

So, I tried mapping "/foo/*" to AxisServlet, and used the following URL with success:

Attempting to use "/*" as the mapping fails, and the documentation even states that this is
not the way to map a default servlet (the first way is).

So, I'm thining this is a bug in Axis when the default servlet mappign is used -- it seems
to be miscalculating how much of the URL to chop off to find the service name.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message