axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srinath Perera (JIRA)" <>
Subject [jira] Commented: (AXIS2-2776) Providing soap address based on request Host header in user provided WSDL
Date Mon, 11 Jun 2007 19:03:25 GMT


Srinath Perera commented on AXIS2-2776:

It may be better to provide proprty in axis2.xml that will be used to find the host Name.
Purposed order to find the host name could be 
1) If property exists, use that
2) try to get host name from request To Address
3) Try to get host name using Java things

> Providing soap address based on request Host header in user provided WSDL
> -------------------------------------------------------------------------
>                 Key: AXIS2-2776
>                 URL:
>             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:
> 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 (2 and 3), 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 a problem in environments when virtual hosting is used, and it represents
a problem too when you have development, testing and production environments with different
hostnames/ips, you are using a custom WSDL and these environments can be queried from different
locations (Internet and Intranet for example).
> For case 2, I've made the attached patch to
> 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
> 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:
For additional commands, e-mail:

View raw message