Hi,
  I'm building an application that uses some configuration
  data in database tables. My JSP's will use this data to
  populate drop-down lists, radio button etc.

  I'm trying to avoid making a database connection everytime a user
  visits a page with config data. My goal is to load all config data
  from the database when the application comes up (tomcat), then
  reference the config data through some method without having to
  make db calls (event w/conn pooling).

  What is the most efficient way of binding this
  configuration data to an application? and is this possible?

  I'd also like to have an "admin" page where an administrator can
  change the config, and have the changes show up on my drop-down
  lists immediately.

  I'd like to do it without bouncing a servlet/jsp container if
  possible.

  My goal is to bind the data to the "application context" so that
  it can be referenced without additional overhead in database calls.

  Any ideas would be appreciated.
  Peter

Have a startup serlvet or jsp that loads when your tomcat comes up and do the logic of storing your configurations in a static hashmap or any data structure (make static object) that fits your needs..

you can specify start up servlets in web.xml.. You specify <load-on-startup>..You can easily find syntax and reference for this on the web.

-- gopal

Maybe use the web.xml file for the webapp. In here it is possible to setup environment variables (as xml). Why don't you use this, everytime the webapp is loaded