
Java Naming and Directory Interface
5
MENTIONS
3
EPISODES
1
PODCASTS
Search complete. 5 mentions across 3 episodes found for "Java Naming and Directory Interface".
Nov 18, 2026
OSS Speaker Series - Java on Guice: Dependency Injection,...
B
46:14Bob LeeGUEST
So juice is broken down into separate modules so you can kind of take what you need.
B
46:18Bob LeeGUEST
The JNDI one is in the core juice because JNDI is in the core JDK already.
B
46:23Bob LeeGUEST
But the spring one is just a separate jar that you can include if you want to use that.
B
46:26Bob LeeGUEST
Same with struts too.
SV-WEB-JUG: Spring 2.5 and Spring Application Platform
R
21:32Rod JohnsonGUEST
But in Spring 2.5, Pitchfork is not required on top of Spring to do at resource injection.
R
21:41Rod JohnsonGUEST
What it gives you is essentially a superset of what you get in Java EE5 because Spring removes the restriction that the component should come from JNDI.
R
21:52Rod JohnsonGUEST
If you're using at resource for injection in a servlet or an EJB, the injection target must come from JNDI, which kind of makes it not so useful for injecting fine-grained objects.
R
22:04Rod JohnsonGUEST
We remove that restriction.
R
22:08Rod JohnsonGUEST
It looks exactly like what you would see in EJB3 examples.
R
22:52Rod JohnsonGUEST
So you can only inject one reference at a time.
R
22:55Rod JohnsonGUEST
There's no sophisticated support for qualifiers.
R
23:00Rod JohnsonGUEST
And bear in mind that if you really want it to be portable, you have to be committed to making every single object that you're going to inject exposed in JNDI, presumably as an EJB.
Glassbox: Automated Troubleshooting
R
48:57Ron BodkinGUEST
There's a lot of web frameworks and it's relatively easy to extend them.
R
49:00Ron BodkinGUEST
You know, more monitoring of caching, more monitoring of JNDI and OR mapping.
R
49:06Ron BodkinGUEST
So, there's lots of additional pieces to monitor.
R
49:09Ron BodkinGUEST
And certainly, one of the things that we've designed is to make it easy to extend the system so that anyone who has a need for one of these could make a contribution back and share it with the community so that we're not writing and debugging monitors for every framework in the world, but it becomes very easy for the community to contribute and maintain its own set.