I am trying to use JNDI to externalize some configuration properties in a web application.
These properties are strings and are environment specific. Because they are impacted by the environment the web application is deployed on, I do not want to include them in the web.xml. In reading the tomcat 5.5 JNDI instructions (http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html) and the mailing lists (http://article.gmane.org/gmane.comp.jakarta.tomcat.user/72768/match=env ironment+entry+5), it seems that creating <Environment> entries under the <GlobalNamingResources> would be ideal for this. Environment values should be accessible container wide and they don't seem to require any reference in the web.xml file. However, my application cannot find any environment entries defined under GlobalNamingResources. They can only be located if the environment entries are defined for the applications context (e.g. <Context><Environment/></Context>). I am using the standard "java:comp/env" name for looking up my env context. Is this incorrect for accessing global resources? Please note: I am using the tomcat admin web application for create the jndi resources. What am I missing? Best regards, Carlos --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
