JNDI Best Practices
As with any distributed program, JNDI clients need to be aware of efficiency concerns to ensure high performance and scalability. Like RMI calls, the WebLogic Server optimizes JNDI lookups from code running in the server's JVM when they are performed. A lookup within the WebLogic Server is a very efficient operation. In essence, it amounts to a direct method call and a data structure lookup. JNDI clients running within the server should not generally bother to optimize their usage of the naming service.
JNDI lookups within the WebLogic Server are highly optimized.
However, remote clients should consider optimizing (minimizing) the number of round trips between the client and server. Like any remote interaction, each naming ...
Get J2EE™ Applications and BEA™ WebLogic Server™ now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
