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 "Rodrigo Ruiz (JIRA)" <ax...@ws.apache.org> on 2006/05/16 17:06:08 UTC
[jira] Created: (AXIS-2478) Adding support for clients with
multiple network adapters
Adding support for clients with multiple network adapters
---------------------------------------------------------
Key: AXIS-2478
URL: http://issues.apache.org/jira/browse/AXIS-2478
Project: Apache Axis
Type: New Feature
Components: Basic Architecture
Reporter: Rodrigo Ruiz
Priority: Minor
>From the "Select the output-network-interface to call an axis-webservice" thread on the axis-user list.
A user wanted to be able to specify the local binding address of its client application. Its firewall configuration prevented some requests from getting to their destination if the source address was not the correct one. As the firewall was not under his control (maybe it was on the remote server side), he needed the ability to choose the correct address, instead of using the default one.
For helping him, I have developed a simple CommonsHTTPSender subclass that allowed the specification of the local bind address by mapping the remote address.
I think it may be useful for other people, and would like to contribute to the project with it.
Does it make sense to include it in future releases?
--
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
[jira] Updated: (AXIS-2478) Adding support for clients with
multiple network adapters
Posted by "Rodrigo Ruiz (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2478?page=all ]
Rodrigo Ruiz updated AXIS-2478:
-------------------------------
Attachment: RoutedCommonsHTTPSender.java
This is the class source code
> Adding support for clients with multiple network adapters
> ---------------------------------------------------------
>
> Key: AXIS-2478
> URL: http://issues.apache.org/jira/browse/AXIS-2478
> Project: Apache Axis
> Type: New Feature
> Components: Basic Architecture
> Reporter: Rodrigo Ruiz
> Priority: Minor
> Attachments: RoutedCommonsHTTPSender.java
>
> From the "Select the output-network-interface to call an axis-webservice" thread on the axis-user list.
> A user wanted to be able to specify the local binding address of its client application. Its firewall configuration prevented some requests from getting to their destination if the source address was not the correct one. As the firewall was not under his control (maybe it was on the remote server side), he needed the ability to choose the correct address, instead of using the default one.
> For helping him, I have developed a simple CommonsHTTPSender subclass that allowed the specification of the local bind address by mapping the remote address.
> I think it may be useful for other people, and would like to contribute to the project with it.
> Does it make sense to include it in future releases?
--
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
[jira] Commented: (AXIS-2478) Adding support for clients with
multiple network adapters
Posted by "Rodrigo Ruiz (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2478?page=comments#action_12412130 ]
Rodrigo Ruiz commented on AXIS-2478:
------------------------------------
After sleeping on this, I think I have changed my mind.
Perhaps, it is better to modify CommonsHTTPSender (and HTTPSender, BTW), and add a "standard" MessageContext property to set the local bind address. This way, the class I developed could be converted into a simple handler that would set this property value.
I think this is a better approach, because it lets open the development of smarter or more complex implementations of the "routing table", and does not force the inclusion of such a very specific solution like the one I have attached.
> Adding support for clients with multiple network adapters
> ---------------------------------------------------------
>
> Key: AXIS-2478
> URL: http://issues.apache.org/jira/browse/AXIS-2478
> Project: Apache Axis
> Type: New Feature
> Components: Basic Architecture
> Reporter: Rodrigo Ruiz
> Priority: Minor
> Attachments: RoutedCommonsHTTPSender.java
>
> From the "Select the output-network-interface to call an axis-webservice" thread on the axis-user list.
> A user wanted to be able to specify the local binding address of its client application. Its firewall configuration prevented some requests from getting to their destination if the source address was not the correct one. As the firewall was not under his control (maybe it was on the remote server side), he needed the ability to choose the correct address, instead of using the default one.
> For helping him, I have developed a simple CommonsHTTPSender subclass that allowed the specification of the local bind address by mapping the remote address.
> I think it may be useful for other people, and would like to contribute to the project with it.
> Does it make sense to include it in future releases?
--
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