Consider the problem of an application scope backing bean containing lookup data from the database. Consider also, that the user will have the ability to add a new value to this otherwise relatively static set of data.
The problem I am dealing with is how best to "invalidate" this bean and refresh with the latest data from the database. I was thinking that maybe we could have a specialized collection class in Shale (or an interface defining new methods) that we could use to help in this regard. Basically the idea would be that every time new data is added to the backing bean (which is a collection), that Shale framework could be notified and take appropriate action. I am a little rusty on Shale. I will be getting the latest source code tonight and taking another look. I was thinking that after the UpdateModelPhase, Shale could reset any backing beans that have been updated (it would know which ones through "observer" pattern.) Might we want to consider something like this in Shale? This is a pretty general problem that might be nice to be able to solve with the extended lifecycle stuff of Shale. If its not apporpriate, I'd still be interested in ideas on how best to deal with this problem. Regards, sean --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
