In article <[EMAIL PROTECTED]>, Joe Germuska <[EMAIL PROTECTED]> wrote:
> Looking back at the original email, I would guess that the things > read from XML config files could pretty safely be stored in each > ServletContext -- assuming they don't change after initialization -- > drop down menus seem to fit that description. I think you're right. I'm going to see if it works. > My other statement, about "using one bean to manage everything in an > application context" certainly didn't mean one *enterprise java* > bean. Like I said, I don't use 'em. But if you have a bunch of > things that go into the application context, you may find it cleaner > to make one "Application" bean which goes into the application > context and which stores all those other things as properties. Then > you never have to worry about making sure all accesses into the > context use the right name, except for one object, and you get > type-safety as much as you want it, and you have a clear interface > for your application object which you could use in testing, etc. Thanks. I'm glad you made sense of my question. :) If I do this, can I still use Struts tags that refer to a bean? Taking the drop-down menu example, if I store it directly in the servletContext, I can do: <html:options collection="menuName" ... > But if I store it in the servletContext as "menus.menuName", can I do something similar? Thanks, Jacob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
