[jboss-jira] [JBoss JIRA] Assigned: (JBAS-4172) Document undocumented naming properties

[Norman Richards (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-4172?page=all ]

Norman Richards reassigned JBAS-4172:
-------------------------------------

    Assignee:     (was: Norman Richards)

> Document undocumented naming properties
> ---------------------------------------
>
>                 Key: JBAS-4172
>                 URL: http://jira.jboss.com/jira/browse/JBAS-4172
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Documentation
>            Reporter: Brian Stansberry
>             Fix For: JBossAS-5.0.0.GA, JBossAS-4.2.0.GA
>
>
> The following properties accepted by org.jnp.interfaces.NamingContext are not covered in the documentation:
> jnp.socketFactory -- The javax.net.SocketFactory impl to use for the bootstrap socket
> jnp.localAddress --  The local (client-side) address to bind the connected bootstrap socket to
> jnp.localPort -- The local (client-side) port to bind the connected bootstrap socket to
> jnp.useRelativeName -- A flag indicating the style of names passed to javax.naming.spi.NamingManager methods. True for api expected relative names, false 
> for absolute names as used historically by the jboss naming implementation.
> jnp.discoveryTTL -- The time-to-live for multicast discovery packets
> The first four belong in the general discussion of org.jnp.interfaces.NamingContext (e.g. Section 2.3.2 of The JBoss 4 Application Server J2EE Reference), while the last belongs in the clustering discussion (Section 2.3.3 of the above as well as Section 1.2.2 of The JBoss 4 Application Server Clustering Guide).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira