As I understand the spec, the Deployer can only edit the environment entries and not the deployment descriptor - that is the responsibility of the Bean Provider and Application Assembler.
Section 22.3 of the EJB 2.0 spec (Deployment Descriptor / Application Assembler's responsibility) says
Each output ejb-jar file is either a deployment unit intended for the Deployer, or a partially assembled application that is intended for another Application Assembler.
Chapter 22 which details the deployment descriptor, has sections about both the Bean Provider, Application Assembler, and Container Provider responsibilities - nothing about the Deployer. Which I take to indicate that the Deployer has no responsibility for the dd, but only for the environment entries (which are read from the dd). [ August 10, 2005: Message edited by: �dne Brunborg ]
since env entry can be used to customize the application, then the deployer who will make your application work on the operational environment, can change the env entry value
since env entry is accessed programmatically, then its meaning is dependent on the provider.....so the bean provider or assembler must inform the deployer on what that env entry is for, so he will give appropriate value....usually via comments on the dd
just my 2 cents
Doe, a deer, a female deer. Ray, a pockeful of sun. Me, a name, I call my tiny ad ...
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop