Currently the only lifecycled thing is component. However I've found components hard to fit in some cases.
Example: at first I created a paging component that would remember current page parameters for a page. I thought that was quite nice, cause I could create a generic puzzle to attach to different actions. Then I've found the first problem - some actions took multiple paging components. Currently webwork only defines that some action may be component aware, but it does so only for a single component. The second problem I ran into was that some actions wanted to influence components creation - that also didn't fit webwork component model that assumes components are handed to actions - yes I know - IOC works that way. So the bottom line was that I needed something different to provide lifecycle. So I designed that simple ScopeInterceptor, that allows you to define that some properties (I mean action's properties) are scoped for session or application lifetime. After action invocation it collects all scoped properties and puts them in appropiate scope attributes. When the action is run again, it initializes it with the previous values from the scope. I've created jira issue for this, and I think it should go into webwork package. I've just noticed that it has that JDK 1.4 String.split() methods that should be probably replaced with something from oro, but other than that it works fine. -- Mike ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
