You don't want it in the session if it's very big! There's no reason to load this data repeatedly (for each user!) if it is non-volatile! Load it on startup as I mentioned in my other post and merely reference it. If it is volatile you'll have to devise some strategy for updating it. Assuming that, when it is updated, you only have one "writer" (we know there are many possible "readers"), you shouldn't have to serialize any access to it. That would be the most straight-forward implementation (you wouldn't really need anything to manage updates). If (parts of) it may be updated by multiple threads, you'll want to either serialize updates to those pieces or take the db hit to retrieve it when you need it.
HTH, Eddie Bill Blackmon wrote: >Thanks. I'll try that. I guess I'd just create an instance of the form bean >class at the entry to the app with the request passed in and create the form >bean in application or session scope? The formbean would be declared in the >struts.xml file with session or application scope? I'm just thinking out >loud. I don't want the form bean to be attached to any action if possible. >I'm new to this so bear with me! > >Thanks, >Bill > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
