Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <7106712.1181144726756.JavaMail.jira@brutus>
Date: Wed, 6 Jun 2007 08:45:26 -0700 (PDT)
From: "Davanum Srinivas (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Assigned: (AXIS2-2776) Providing soap address based on
 request Host header in user provided WSDL
In-Reply-To: <719936.1181143406338.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas reassigned AXIS2-2776:
---------------------------------------

    Assignee: Deepal Jayasinghe

> Providing soap address based on request Host header in user provided WSDL
> -------------------------------------------------------------------------
>
>                 Key: AXIS2-2776
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2776
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.3, 1.2, nightly
>         Environment: Tested on Linux, Tomcat 6.0.10, Sun JDK 5. Patch included should work in any environment as well.
>            Reporter: Luis Mariano Luporini
>            Assignee: Deepal Jayasinghe
>             Fix For: nightly
>
>         Attachments: AxisService.java.patch
>
>
> When Axis2 must respond to a ?wsdl request, there are three possible scenarios in which soap:address is calculated and given back inside the generated WSDL.
>        1. User provided WSDL with parameter  modifyUserWSDLPortAddress set to false
>        2. User provided WSDL with parameter  modifyUserWSDLPortAddress set to true
>        3. On the fly WSDL generation
> In case 1 the soap:address in the response is left unaltered and the original WSDL without modifications is given to the client.
> In the other two cases (1 and 2), Axis2 is currently using the first available IP address in the server to complete (or replace) the hostname part of the generated soap:address in the WSDL. This is problem in environments when virtual hosting in using, and it represents a problem too when you have development, testing and production environment with different hostnames/ips, you are using a custom WSDL and this environments can be queried from different locations (Internet and Intranet for example).
> For case 2, I've made the attached patch to AxisService.java.
> This patch uses the provided info in Host header of the HTTP request (if provided) to generate the soap:address info inside WSDLs.
> Case 1 is really different and there are different ways to solve it. I think I'd need more time to get to understand how all this works and then I'll be able to take at least a reasonable solution. There is a JIRA about this case but it's unassigned sadly:  AXIS2-2720 <http://issues.apache.org/jira/browse/AXIS2-2720>.
> Thanks.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org