axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1397) Services overview page has incorrect link to service-wsdl if using a mapping other then /services
Date Wed, 16 Jun 2004 16:44:21 GMT
The following comment has been added to this issue:

     Author: AJ Banck
    Created: Wed, 16 Jun 2004 9:43 AM
I could update AxisServlet and replace:
        String baseURL = getWebappBase(request)+"/services/";

        String baseURL = getWebappBase(request)+ request.getServletPath() +"/";

Might be a bit weird as this is the only location getWebappBase is used. Alternative is adding
a methods to AxisServletBase using getRequestURI but that seems more overhead then needed.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1397
    Summary: Services overview page has incorrect link to service-wsdl if using a mapping
other then /services
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             WSDL processing
             current (nightly)

   Reporter: AJ Banck

    Created: Wed, 16 Jun 2004 9:24 AM
    Updated: Wed, 16 Jun 2004 9:43 AM

The URL location to the services is hardcoded to '/services' in the generated page of available
AxisServlet.reportAvailableServices[455] has:
        String baseURL = getWebappBase(request)+"/services/";

This path is defined in the mapping of web.xml So if the web.xml has a mapping on another
url, the services overview doesn't work.

For example, we have different URL's for different versions of the application's API. This
maps the services like:

With this the {baseurl}/api4/services shows the overview of services, but clicking on one
of the WSDL  links  (linking to {baseurl}/services/myservice?wsdl}throws a 404.
The wsdl is available at {baseurl}/api4/services/myservice?wsdl

Not sure what the best solution is. Can AxisServlet find out what the mapping used is, or
should it be a variable?

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