axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maslakov Denis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4519) Supporting of different configurations for different requests is broken for AxisServlet.
Date Thu, 08 Oct 2009 07:57:31 GMT

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

Maslakov Denis commented on AXIS2-4519:
---------------------------------------

Hi!

<transportReceiver name="http" 
                       class="org.apache.axis2.transport.http.AxisServletListener"> 
        <host name="myservice1.host.com" port="80" /> 
        <host name="192.168.0.1" port="8080" /> 
        <host name="myservice3.host.com" port="9090" /> 
</transportReceiver> 

Can do these setting for AxisServletListener?

When an user requests service through the myservice1.host.com/context1/service/WSService/,
then the EPR will be built using the parameter myservice1.host.com with port 80.

When an user requests service through the 192.168.0.1/context2/service/WSService/, then the
EPR will be built using the parameter 192.168.0.1 with port 8080.

When an user requests service through the myservice3.host.com/context2/service/WSService/,
then the EPR will be built using the parameter myservice3.host.com with port 9090.

Then do not have to propagate the port and the URL in the context, and the EPR can be created
once for each configuration specified for the AxisServletListener.


> Supporting of different configurations for different requests is broken for AxisServlet.
> ----------------------------------------------------------------------------------------
>
>                 Key: AXIS2-4519
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4519
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: kernel, transports
>    Affects Versions: nightly
>         Environment: FreeBSD 6.2, Apache 2.22, Diablo JDK 1.5, Tomcat 6.0.14
>            Reporter: Maslakov Denis
>
> AxisServlet does not support different configurations for different requests for one
instance of Axis2 web-services under Tomcat.
> The configuration of web-services is:
> 1. The frontend is Apache web-server on 80 port.
> The Apache contains virtual domain (webservices.domain.ru) for redirecting request to
Tomcat (through mod_jk).
> The request for web-service is http://webservices.domain.ru/context-path1/services/WSService/
> 2. The backend of web-services is Axis2 under Tomcat on 8180 port.
> The request for web-service is http://<ip>:8180/axis2-test/services/WSService/
> Here axis2-test is name of webapp Axis2 and so context path.
> The external users inquire web-service from Apache.
> The internal users inquire same web-services directly from Tomcat.
> Nevertheless, class AxisServletListener will catch port from the first request of user.
If it will be request from external user, then port will be 80 for all users. If it will be
request from internal user, then port will be 8180 for all users.
> The context path from request also will be different.
> It happens as AxisServlet instance contains only one listener and one path of context.

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


Mime
View raw message