Search...
FAQs
Subscribe
Pie
FAQs
Recent topics
Flagged topics
Hot topics
Best topics
Search...
Search within EJB and other Jakarta /Java EE Technologies
Search Coderanch
Advance search
Google search
Register / Login
Post Reply
Bookmark Topic
Watch Topic
New Topic
programming forums
Java
Mobile
Certification
Databases
Caching
Books
Engineering
Micro Controllers
OS
Languages
Paradigms
IDEs
Build Tools
Frameworks
Application Servers
Open Source
This Site
Careers
Other
Pie Elite
all forums
this forum made possible by our volunteer staff, including ...
Marshals:
Campbell Ritchie
Jeanne Boyarsky
Ron McLeod
Paul Clapham
Liutauras Vilda
Sheriffs:
paul wheaton
Rob Spoor
Devaka Cooray
Saloon Keepers:
Stephan van Hulst
Tim Holloway
Carey Brown
Frits Walraven
Tim Moores
Bartenders:
Mikalai Zaikin
Forum:
EJB and other Jakarta /Java EE Technologies
JNDI
sitaram irrinki
Ranch Hand
Posts: 158
posted 18 years ago
Number of slices to send:
Optional 'thank-you' note:
Send
If there are 100 beans in JNDI & the context.lookup() method takes time to lookup. how can we handle the situation to make it easy retrieval of the bean
Valentin Tanase
Ranch Hand
Posts: 704
posted 18 years ago
Number of slices to send:
Optional 'thank-you' note:
Send
Check the EJBHomeFactory design
pattern
.
Regards.
I think, therefore I exist -- Rene Descartes
We should throw him a surprise party. It will cheer him up. We can use this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
reply
Bookmark Topic
Watch Topic
New Topic
Boost this thread!
Similar Threads
Regarding JNDI
context.lookup() performance isuue
pls answer this
Caching ejb 3 bean lookups
Does a stateless session bean have access to the User Principal?
More...