[
https://issues.jboss.org/browse/AS7-4296?page=com.atlassian.jira.plugin.s...
]
Stephen McConnell commented on AS7-4296:
----------------------------------------
Relevant extract from the JEE6 spec supporting this requirement:
EE.5.2 JNDI Naming Context
The application component’s naming environment is a mechanism that allows
customization of the application component’s business logic during deployment
or assembly. Use of the application component’s environment allows the
application component to be customized without the need to access or change
the application component’s source code.
5.2.1 (3) The Deployer uses the tools provided by the container to initialize
the environment entries that are declared in the application component’s
deployment descriptor or via annotations. The Deployer can set and modify
the values of the environment entries. As part of this process, the Deployer
is allowed to override any “lookup” information associated with the application
component.
The overriding of environment entries needs to be available as a part of a deployment
descriptor (i.e. invoked as part of an automated process).
Support overriding deployment descriptors at deployment time
------------------------------------------------------------
Key: AS7-4296
URL:
https://issues.jboss.org/browse/AS7-4296
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management, Server
Affects Versions: 7.1.1.Final
Reporter: Stuart Douglas
Assignee: Stuart Douglas
We need to be able to specify alternate jboss-*.xml descriptors (or indeed any
descriptor) at deployment, and have them override the descriptors physically present in
the deployment archive.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira