JNDI Bindings

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

JNDI Bindings

Heiko Braun


Can somebody enlighten me?

What JNDI namespaces are allowed for explicit JNDI bindings  (i.e datasources, resource adapters)

Looking at the docs it seems that you could either chose 'java:global/<xyz>' or 'java:jboss/<xyz>'.
Whereas the 'java:module' and java:app' namespaces seem to be reserved implicit bindings.
Is that correct?


Ike



_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
Reply | Threaded
Open this post in threaded view
|

Re: JNDI Bindings

David Lloyd-2
On 07/20/2011 07:31 AM, Heiko Braun wrote:
>
>
> Can somebody enlighten me?
>
> What JNDI namespaces are allowed for explicit JNDI bindings  (i.e datasources, resource adapters)
>
> Looking at the docs it seems that you could either chose 'java:global/<xyz>' or 'java:jboss/<xyz>'.
> Whereas the 'java:module' and java:app' namespaces seem to be reserved implicit bindings.
> Is that correct?

Not exactly.  The reason that "java:module/" and "java:app/" are not
available at the global configuration level is that every deployment has
their own distinct instance of these namespaces (more or less; all
modules within an EAR share the "app" namespace), just as every
component has its own "java:comp/" namespace (more or less; there's some
goofy extra rules about servlets that exist for historical purposes).

For now we only allow binding to global namespaces from global
configuration.  It is conceivable that we could allow binding to
per-app/module/comp namespaces too, someday, _if_ someone had a good
enough reason for it (I can't think of one myself).

--
- DML
_______________________________________________
jboss-as7-dev mailing list
[hidden email]
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev