Details
-
Feature Request
-
Resolution: Done
-
Major
-
JBossAS-4.0.2 Final
-
None
Description
Currently, we do not support the Tomcat notion of GlobalNamingResources. In Tomcat, you can put something like this in your server.xml.
<GlobalNamingResources>
<Environment name="oncall/system/mode"
type="java.lang.String"
value="PRODUCTION"/>
</GlobalNamingResources>
Then, in every web context, the name and value will be bound in JNDI at java:comp/env. This is equivalent to this in web.xml:
<env-entry>
<env-entry-name>oncall/system/mode</env-entry-name>
<env-entry-value>PRODUCTION</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
The advantage of having this in server.xml is that you don't have to add the env-entry in every web.xml file. The customer in case 4042 brought up this use case when they were porting from standalone Tomcat to JBoss AS.
Attachments
Issue Links
- is related to
-
JBAS-29 Added URL Service MBean
- Closed