[
https://jira.jboss.org/jira/browse/JBNAME-25?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBNAME-25.
---------------------------------
Resolution: Done
The following changes were made to support the IPv6 addresses:
1. Change the Naming cache to use InetSocketAddress as the key rather than the host +
":" port string.
2. Add an alternate host + "@" port url syntax so that one can specify an ipv6
address and a port.
3. If there are multiple ':' in a provider url, we have to assume its an IPv6
address with no port. The only way a port can be specified with an IPv6 address is by
using the '@' separator as in:
::ffff:127.0.0.1@1099
[ Show ยป ]
Scott M Stark - 21/Jan/09 08:29 PM The following changes were made to support the IPv6
addresses: 1. Change the Naming cache to use InetSocketAddress as the key rather than the
host + ":" port string. 2. Add an alternate host + "@" port url syntax
so that one can specify an ipv6 address and a port. 3. If there are multiple ':'
in a provider url, we have to assume its an IPv6 address with no port. The only way a port
can be specified with an IPv6 address is by using the '@' separator as in:
::ffff:127.0.0.1@1099
Add support for parsing IPv6 addresses in
org.jnp.interfaces.NamingContext
--------------------------------------------------------------------------
Key: JBNAME-25
URL:
https://jira.jboss.org/jira/browse/JBNAME-25
Project: JBoss Naming
Issue Type: Feature Request
Components: jnp-client, jnpserver
Reporter: Dimitris Andreadis
Assignee: Scott M Stark
Fix For: 5.1.0.Beta1
Same as JBAS-6390 for the broken out naming project
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira