You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2010/12/19 05:10:01 UTC
[jira] Resolved: (AXIS2-3143) WSDL Port Address generation
algorithim has major limitations
[ https://issues.apache.org/jira/browse/AXIS2-3143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samisa Abeysinghe resolved AXIS2-3143.
--------------------------------------
Resolution: Fixed
As per last comment
> WSDL Port Address generation algorithim has major limitations
> -------------------------------------------------------------
>
> Key: AXIS2-3143
> URL: https://issues.apache.org/jira/browse/AXIS2-3143
> Project: 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org