I would be glad to help writing / testing this feature.
Is the code available somewhere ?
I also just have one question: when I was looking at how to use Geronimo
JNDI implementation, i faced the problem that to access one of the proxy
in the JNDI tree, Geronimo requires the main interface name (which is
usually given by deployment descriptors). How did you work around that ?
Cheers,
Guillaume Nodet
Krishnakumar B wrote:
Hi,
In geronimo road map there was a requirement for implementing Global
JNDI for geronimo.
An approach to implementing the same is posted below. Kindly post your
valuable feedback.
* Write and Deploy a GBean For Global JNDI
* GBean on startup of server would introspect the server and build JNDI tree
- jdbc
- jms
- ejb etc...
* JNDI tree is stored in Hashmap and we can use
ComponentContextBuilder to build this tree.
* We can use EnterpriseNamingContext to create a context.
* The Context is stored as a static variable in the Local Factory Class.
* During deployment a new entry is added to Context ( Hashmap.)
* During undeployment an entry is removed from Context ( Hashmap )
* We can reuse the existing the geronimo-naming package for directory
operations.
We have done some initial ground work ( Writing Gbean, Building JNDI
Tree ) and would be glad to know how such an implementation would fit
into geronimo server, limitations if any so that we know we are using
the right approach.
Regards
Krish
