JNDI auto-Bind on Startup

Question

I have a EJB 3 application that is using JNDI to use an LDAP server. However the application will be deployed in an environment where the LDAP server information (especially authentication) will not be available to it.
I have read that JNDI does not persist objects across server shutdown, so what I'd like to do is store the LDAP server specifics in a config file that will automatically be bound to the JNDI start when JBOSS starts. Ideally this would not require me to know anything about the implementation environment and could be a 'hands off' approach where as long as the file exists in the JBOSS directory the names will automatically bind.
Is there a way to bind a JNDI object at JBOSS startup (similar to the way you would define a datasource) in a seperate file and then lookup that predefined object, extract the LDAP server information and use it?
I am imagining something along the lines of this
InitialContext ctx = new InitialContext();
LDAPConfigParams configParams = (LDAPConfigParams) ctx.lookup( "LDAPParams" );
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, configParams.getContextFactory());
env.put(Context.PROVIDER_URL, configParams.getUrl());
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, configParams.getUserName());
env.put(Context.SECURITY_CREDENTIALS, configParams.getPassword());
env.put("java.naming.ldap.attributes.binary", "objectGUID");
InitialContext ldapContext = new InitialContext( env );
// use ldapContext as normal here

Answer 1

Although no one was able to help me, the lack of responses inspired me to look into other solutions.
JBoss supports JMX through mbeans. mbeans are managed by JBoss at startup time. There are (at least) two types of mbeans available in JBoss. I decided to extend a SubDeployerSupport mbean and implementing the XSLSubDeployerMBean. This enables me to get a hook into each new item being deployed (file added/modified) into the deploy directory.
You can configure the files it looks at by overriding the accepts(DeploymentInfo) method to filter out files that don't match on the particular suffix your interested in.
I created a custom xml file for my LDAP data sources that has the extension -ldap.xml, and configured my accepts function to trigger init on these types of functions. This gives me a hook into the config files of type -ldap.xml (either at boot or redeploy). I can then extract the XML and create JNDI objects corresponding to my LDAP config.
The only downside to this is that it ties me to the JBoss application server. Can anyone suggest a similar way to do this without requiring JBoss?