[
https://issues.apache.org/jira/browse/AXIS2-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12521902
]
Davanum Srinivas commented on AXIS2-3143:
-----------------------------------------
that's what we do (in Axis2 1.3) -
http://marc.info/?l=axis-cvs&m=118499936203494&w=2
> WSDL Port Address generation algorithim has major limitations
> -------------------------------------------------------------
>
> Key: AXIS2-3143
> URL: https://issues.apache.org/jira/browse/AXIS2-3143
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Haneef Ali
>
> PortAddress generation from the wsdl has serious limitations
> 1) If you have multiple network address, then we can't predict the address
> 2) Using the hostname parameter in axis.xml is not a solution for the
> following reason
> 1) If you hardcode hostname, then you need to create different
> build for deploying in different machine
> 2) In production normally you have clusters of servers. Each server
> in the cluster will be running in the different machine. In this case
> hardcoding hostname is not a solution
> 3) Normally application servers will be in their own DMZ and are
> fronted by a webserver. In this case , you need the address of the webserver
> and not that of the application server.
> Proposed solution
> 1) Get the hostname from the request and use that to generate wsdl
> portAddress. As far as I know this is what weblogic does.
> Thanks,
> Haneef
>
--
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]
