Specifying java.naming.factory.initial and java.naming.provider.url for default in-container InitialContext ----------------------------------------------------------------------------------------------------------- Key: JBAS-4668 URL: http://jira.jboss.com/jira/browse/JBAS-4668 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mike Millson Allow for a reference to the static NamingContext.localServer field to be returned from the org.jnp.interfaces.NamingContext.checkRef(Hashtable) method for a given java.naming.provider.url. Use cases exist where applications use property files to specify JNDI connection properties such as java.naming.factory.initial and java.naming.provider.url. The apps are written in such a way that require these properties be explicitly defined, even though the default in-container initial context is what will be used. Customers are currently specifying something like: java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.provider.url=jnp://abcxyz:1099/ However, this approach has several drawbacks, including: 1) Server names are hard-coded in property files, which reduces deployment flexibility 2) This approach appears to use a socket connection, which is probably not as efficient as the in-container initial context. For these use cases, customers would like to specify a value java.naming.factory.initial and java.naming.provider.url that will result in the default in-container InitialContext being used. Not specifying any properties will give this context, but the way some applications are written, something needs to be passed. -- 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