Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[patch] a guice based JNDI provider #259

Closed
gissuebot opened this issue Jul 7, 2014 · 2 comments
Closed

[patch] a guice based JNDI provider #259

gissuebot opened this issue Jul 7, 2014 · 2 comments

Comments

@gissuebot
Copy link

From james.strachan on October 09, 2008 07:26:34

This patch provides a Guice based JNDI provider. While Guice Ioc is a general replacement for
JNDI - there are times when developers need to work with JNDI (e.g. for JSR250/EJB3 or legacy
reasons) and sometimes there is value in some kind of Registry or Service Locator pattern.

So this patch provides a JNDI provider which uses Guice to create an Injector from one or more
modules and then exposes the bindings from the injector into JNDI. This lets you use Guice to
fully create the entire JNDI context in a simple easy way letting folks use Guice for all their IoC
needs while using JNDI if it is required.

I can't create wiki documents in guice so for now I've created a wiki document in another project
to describe how to use this JNDI provider and how to bind Guice bindings to JNDI https://code.google.com/p/camel-extra/wiki/GuiceJndi

Attachment: gist
   a_guice_jndi_provider.patch

Original issue: http://code.google.com/p/google-guice/issues/detail?id=259

@gissuebot
Copy link
Author

From james.strachan on October 13, 2008 07:32:01

I'm not sure if this patch really needs to be in the Guice project or not. In the meantime I've committed it to this
guice-utilities project... https://code.google.com/p/guiceyfruit/ See: https://code.google.com/p/guiceyfruit/wiki/GuiceyJndi

@gissuebot
Copy link
Author

From limpbizkit on October 15, 2008 08:11:19

(No comment was entered for this change.)

Status: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant