You need an indirection layer similar to that which exists for J2EE components.
You would have to create an indirection manager mbean that bound an object
factory under the static namespace prefix you wanted to use with the configurations
like the DatabaseLoginModule(e.g., admin/static) and then you register the mappings
you want handled. So for the example below, you would use admin/static/LOGIN_DB
in the DatabaseLoginModule and register the mapping from LOGIN_DB -> java:jdbc/MAIN_DB
with the indirection manager mbean. It could be done via JMX invocations or
simply by having the indirection manager mbean monitor a mapping file.
----- Original Message -----
From: "Ferguson, Doug" <[EMAIL PROTECTED]>
To: "JBoss User (E-mail)" <[EMAIL PROTECTED]>
Sent: Monday, June 25, 2001 11:48 AM
Subject: [JBoss-user] datasource jndi mapping
> Hey,
>
> I ran this message awhile back and got no response.
> If you have any inclination to an answer... please respond.
>
> I have am interested in mapping datasource jndi names at deploytime..
> However I want to make these mappings apply to the global namespace.
>
> The reason:
> For example, in order to use the current DatabaseLoginModule you must
> provide a jndiName for the datasource to use. Since the login module
> is not a bean and doesn't have acces to the java:comp/env we must
> use the global namespace. Therefore I have to use the jndi name that is
> in my jboss.jcml. I'd like to be able to map the name in jboss.jcml say
> java:jdbc/MAIN_DB to java:jdbc/LOGIN_DB
>
> Any comments suggestions?
>
> d.
>
> _______________________________________________
> JBoss-user mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-user
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
