[
http://issues.apache.org/jira/browse/AXIS2-460?page=comments#action_12369391 ]
Deepal Jayasinghe commented on AXIS2-460:
-----------------------------------------
How about the following approach ,
when we generate replyTo ERP we first check for a particular parameter (say
its name is hotsName) then if that present rather than getting IP using
getHostByName() we can use that parameter value to generate EPR.
So if some one want running behind the ADSL or smt then he can configure his
transport as follows
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port" locked="false">6060</parameter>
<parameter name="hotsName" locked="false">www.company.com</parameter>
</transportReceiver>
> Ability to override hostname and port in EPRs
> ---------------------------------------------
>
> Key: AXIS2-460
> URL: http://issues.apache.org/jira/browse/AXIS2-460
> Project: Apache Axis 2.0 (Axis2)
> Type: Improvement
> Components: transports
> Reporter: Paul Fremantle
>
> Add a parameter to transports that allow the IPAddress/Hostname that is used
> in EPRs to be overridden. For example, if I am on a server behind a firewall,
> the getHostByName() will reply something like 10.0.0.2, but the real
> addressable name may be www.company.com.
> Similarly with a replyTo, I may have a ADSL NAT router in front of my
> client., so my machine's IP is called 192.168.1.2, but the addressable IP is
> myserver.dyndns.org.
> So we need to be able to configure transports. Similarly the port maybe
> changed, so that also needs the ability to override.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
