This is an interesting question. Using the PlugIn interface to store "semi-static" data in the app context is a commonly accepted pattern (we use it in the project I'm working on now). However, there's no mechanism currently available in Struts to allow for data model change event notification (evidently, that's the major difference between Struts & Barracuda, from what little I understand of Barracuda). I'd personally love it if there were a simple mechanism available to Struts for just such event notification.
In the meantime, you may want to store such data in session scope, as it's more "volatile" (periodically speaking). I don't know the nature of your data, but if it isn't a huge amount, it shouldn't be a problem.
Keep us posted on your progress.
Curtis -- cee dot tee at verizon dot net
Mike Duffy wrote:
Thanks Christian,
Let me give you a specific example of what I am trying to do.
I have several different sets of label/value pairs that are stored in database tables. These label/value pairs make up the select options and other interface options for web pages in the application. The options do not change that often, so rather than going back to the database each time a page is displayed, I'd like to store the options in maps that are stored in application scope and easily accessible through JSTL.
On the occasion that the options do change, I'd like to reload the applicable maps to all servers
in the cluster.
It seems like this would be a good feature for Tomcat to have, but from reading the documentation it seems that the feature is not there.
Perhaps some sort of JMS broadcast service would do the trick. Does any one have any suggestions?
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
