[
https://issues.apache.org/jira/browse/GERONIMO-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483716
]
Aman Nanner commented on GERONIMO-2971:
---------------------------------------
I have attempted to integrate the Global JNDI plugin into my 1.2 sandbox so
that I can use the {{org.apache.geronimo.gjndi.binding.EjbBindings}} GBean to
auto-bind all my EJBs into JNDI. However, it seems as though that the
{{EjbBindings}} context itself does not get bound as a nested context to the
"java:" context, and so it is not accessible via JNDI.
I had tried modifying the EjbBindings class so that it would add itself to the
"java:" namespace using the following steps:
1) Accessing the top-level global context by calling
{{GlobalContextManager.getGlobalContext()}}.
2) Calling {{lookup( "java:" )}} on the global context to get the "java:"
{{WritableContext}}.
3) Adding the {{EjbBindings}} context to the "java:" {{WritableContext}}.
Unfortunately, once the "java:" {{WritableContext}} is bound to the
{{GlobalContext}}, it becomes unmodifiable, and so I can't bind anymore
contexts to it (presumable for security reasons).
> Auto bind resources to Global JNDI
> ----------------------------------
>
> Key: GERONIMO-2971
> URL: https://issues.apache.org/jira/browse/GERONIMO-2971
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Affects Versions: 2.0
> Reporter: Christopher M. Cardona
>
> We need a way to auto bind resources like JDBC DataSource, JavaMail Session,
> EJB, etc. to Global JNDI namespace. This will allow the lookup of the said
> resources without declaring resource references in the deployment plans.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
