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?
Well, two things -- first, in most places in Struts, you can use the combination of the "name" attribute and the "property" attributes to dereference properties of beans; see http://jakarta.apache.org/struts/userGuide/struts-html.html#options for this specific case.
But second, despite what I said, I have found the specific case of once-initialized collections of menu items to be a suitable exception to my "rule" about using one bean to encapsulate all of your application logic or session state. This is mostly because I use the DigestingPlugIn class which makes it very easy to turn XML into an object in application scope.
I guess there's an exception to every rule!
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
