[
https://jira.jboss.org/jira/browse/JBNAME-19?page=com.atlassian.jira.plug...
]
Scott M Stark resolved JBNAME-19.
---------------------------------
Resolution: Done
The Naming server instance can now be specified via the following in order of priority:
1. Via a Naming instance passed in under the InitialContextFactory env
NamingContext.JNP_NAMING_INSTANCE property (= jnp.namingInstance)
2. Via a Naming instance injected into the LocalOnlyContextFactory instnace
3. Via a Naming instance bean name specified via the InitialContextFactory env
NamingContext.JNP_NAMING_INSTANCE_NAME property (= jnp.namingInstanceName)
4. Via the JVM global NamingContext.getLocal() value
Allow the Naming instance to be injected into the
LocalOnlyContextFactory
-------------------------------------------------------------------------
Key: JBNAME-19
URL:
https://jira.jboss.org/jira/browse/JBNAME-19
Project: JBoss Naming
Issue Type: Feature Request
Components: jnp-client
Affects Versions: 5.0.0.CR3
Reporter: Scott M Stark
Assignee: Scott M Stark
Fix For: 5.0.0.GA
We should allow the Naming instance to be injected into the LocalOnlyContextFactory so
that it can operate with a Naming instance other than the JVM global instance set on the
NamingContext.
--
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