After some pondering, coding and some enlighment (thanks Gavin!), I have two suggestions.
I have found myself wanting to keep per-page state, just as you would do in ye olde days by putting the complete state in the URL-arguments. This can now easily be done by useing PAGE-scoped data. I however want to keep the page-state intact even if I don't use the PAGE-scoped data during an action. Therefore I suggest that a new Scope is intruduced; the CONTINUOUS_PAGE scope, by this I mean that the data should be added to the next PAGE-scope even if the data is not outjected, just as it would in a CONVERSATION. The same can today be achieved by adding | @In @Out | private PageScopedComponent pageScopedComponent; | to all action-beans. The second Scope I'd like to see is a STATIC_CONVERSATION scope. What I mean with this is a Scope connected to a trail of page (conversation) but it behaves like the Session-scope; it's just there and it cannot be started or stopped with @Begin/@End. I think that this could be very usefull, especially if the kill-all-conversations() method is intruduced. Just my 5c, /Magnus View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929744#3929744 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929744 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
