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 "Michele Mazzucco (JIRA)" <ji...@apache.org> on 2008/01/25 13:51:34 UTC
[jira] Created: (AXIS2-3477) allow users to customize the
transportReceiver(s) port
allow users to customize the transportReceiver(s) port
------------------------------------------------------
Key: AXIS2-3477
URL: https://issues.apache.org/jira/browse/AXIS2-3477
Project: Axis 2.0 (Axis2)
Issue Type: Improvement
Components: kernel
Affects Versions: 1.3
Reporter: Michele Mazzucco
It's very common to use HTTP as transport. The problem is that sometimes more than one axis2 instance runs on the same machine (one or more clients, or one client and one server -- especially during development/test).
It would be nice to decide which port the transport receiver should use without providing a custom axis2.xml file every time. The scenario I've just described happens quite often because most of the time all the default settings are fine apart from the port (i.e. the second instance would throw a BindException or a firewall prevents the user to use the default -- 6060 -- port).
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org