Weird, but possible, I guess. :)
Thanks,
Aaron
On 8/11/06, David Blevins <[EMAIL PROTECTED]> wrote:
So check this idea out -- you'll flip. What if we use the
context.xml to override the class that registers the root java: jndi
provider :) Dain and I were going back and forth on what would be
the easiest way to slice in something that could also work for 1.1.x
and that was the best we came up with. You basically override the
jndi provider with one that will first check for objects that are
"java:comp/jpa/(persistence-unit-name)" and delegate that to the
special JPA plugin functionality. Notice I've used "java:comp/jpa"
instead of "java:comp/env/jpa". The idea being that it's a global
thing and not specific to an ENC of a component. This new JNDI
provider would not be JPA specific either, it would require a
reference collection of things that implemented javax.naming.Context
or perhaps as an alternate javax.naming.spi.ObjectFactory. You could
actually register a hole bunch of them and add all sorts of extended
jndi ability via other gbeans and plugins.
-David
