• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Bear Bibeault
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Jj Roberts
  • Carey Brown
Bartenders:
  • salvin francis
  • Frits Walraven
  • Piet Souris

container role in environment entry settings?

 
Ranch Hand
Posts: 257
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The container is responsible for providing tools, which helps a Deployer to set or modify environment entry values.

is above statement is correct?
environment entries are defined by bean provider in ejb-jar.xml file. Assembler can set or change environment entry values.
But why container and deployer are coming in to picture. can a deployer change environment entry values?

Yamini.
 
Cowgirl and Author
Posts: 1589
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Howdy -- a Deployer could definitely modify environment variables--in fact, we like to think of env variables as "deploy-time constants", because they are typically things that might vary from deployment to deployment (tax rates, discounts, etc.)

The Container just has to make sure that this is available for a deployer to modify. There is a good chance that the bean provider and possibly the app assembler do not *know* the real value until deploy-time.

cheers,
Kathy
 
Do you want ants? Because that's how you get ants. And a tiny ads:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic