This week's book giveaway is in the OCP forum. We're giving away four copies of OCP Oracle Certified Professional Java SE 11 Developer Practice Tests and have Scott Selikoff and Jeanne Boyarsky on-line! See this thread for details.
Hi gowher amin naik I think <env-entry> is provided by assembler <container-transaction> is provided by bean provider <ejb-link>,<role-link>,<security-identity> is provided by assembler <assembler-descriptor> tag are provided by assembler.
<env-entry> If the Bean Provider provides a value for an environment entry using the env-entry-value element,the value can be changed later by the Application Assembler or Deployer
<transaction-attributes> The Application Assembler may define the value of the transaction attributes for the methods of the home and component interfaces of the enterprise beans that require container-managed transaction demarcation.
According to me(word primarily is important) Value for env-entry is primarily provided by Bean Provider.
Value for transaction-attributes is primarily provided by Deployer.
It's correct that <env-entry> tag is provided by Bean provider who writes an arbitrary value in <env-entry-value> tag. It's assembler who actually modifies value in <env-entry-value> tag, so that it fulfills requirement of a particular application.
All the tags inside <assembly-descriptor> are provided by Assembler. Eception is <container-transaction>. It's deployer who puts this tag. Only deployer may decide whether a bean would use a CMT or BMT.