• 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 ...
  • Campbell Ritchie
  • Devaka Cooray
  • Knute Snortum
  • Paul Clapham
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar
  • Tim Holloway
  • salvin francis

env-entry configurable at deployment time  RSS feed

Ranch Hand
Posts: 57
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I have a web-app with several env-entry's. I would like to configure the values for the env entries after I have deployed the application (Websphere 5.0/5.1). Is this possible?

I tried to find documentation for "Resource Environment Providers" and "Referenceables", if this solves my problem, but no luck. Has anybody an idea how to use this feature?

Ranch Hand
Posts: 52
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
the only way to get updates to env-entries in a webapp in websphere is to reload the webapp - i.e. you may need to restart your application.

if you want to be able to configure environment properties after you've deployed an application, but *not* restart your app, then one good option for websphere is using the JNDI namespace. WebSphere has a whole raft of configuration options for it's cache of JNDI namespace bindings that will let you change the values of variables bound to JNDI names and get the latest settings at runtime. Cache options are on/off, entry time to live, manual refresh, etc,


Consider Paul's rocket mass heater.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!