[ 
https://issues.apache.org/jira/browse/AXIS2-4776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12889689#action_12889689
 ] 

Deepal Jayasinghe commented on AXIS2-4776:
------------------------------------------

As I remember correct this is due to the way we process the URL, we get the URL 
string and try to find the index of data (in your case), and based on that we 
find the service name and operation name. So, I agree with you that it gives 
rise to some issues, but you have a workaround until we properly fix it.

Deepal

> roblem when hostname matches axis service URL path
> --------------------------------------------------
>
>                 Key: AXIS2-4776
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4776
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>         Environment: Windows server 2008, axis2 1.5.1
>            Reporter: Charles Galpin
>
> I changed my axis2 (1.5) service url to /data/MyService instead of
> /axis2/services/MyService by doing the following
> 1. deleted the default tomcat ROOT web service and renamed axis2 to ROOT
> 2. In web.xml I added
> <servlet-mapping>
> <servlet-name>AxisServlet</servlet-name>
> <url-pattern>/data/*</url-pattern>
> </servlet-mapping>
> 3. In axis2.xml I set the parameter
> <parameter name="servicePath">data</parameter>
> This works fine except if the hostname starts with "data". So the following
> works
> http://axis2.myservices.com/data/MyService?wsdl
> http://feeddata.myservices.com/data/MyService?wsdl
> but
> http://data.myservices.com/data/MyService?wsdl
> http://datafeed.myservices.com/data/MyService?wsdl
> fails with "Requested resource not found!" from axis and no errors in the
> logs.

-- 
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]

Reply via email to