Hi all,
I looked at the TurbineNamingService, but I can't seem to figure out if I
should be using it or not. I have code like this:
javax.naming.Context initCtx = new
InitialContext();
javax.naming.Context envCtx =
(javax.naming.Context) initCtx.lookup("java:comp/env");
String emailDataStoreToAddress =
(String)
envCtx.lookup("inventory/EmailDataStoreToAddress");
This code is starting to crop up in lots of places. Does the
TurbineNamingService help with this? It doesn't seem to, but I can't tell
from the howto at:
http://jakarta.apache.org/turbine/turbine-2.2.0/services/naming-service.html
, that doesn't seem to reference it. Unless the service is just to hook up
to JNDI?
It seems that it would be nice to be able to tell TurbineNamingService to
get all values that start with "inventory" or something.. And just cache
them locally in a hashtable. Would that be faster then using JNDI every
time?
Eric Pugh
