>> Doh! This wouldn't be the raison d'etre for the Scope plugin by any chance?
Exactly! I think scope plugin solves your problem. The conversation support in scope plugin is not as rich as that in seam, but can serve as the starting point. I have fixed a couple of bugs in the scope plugin and I am working on some enhancements in scope plugin to take care of nested conversations, fork, join etc. Don't have time to commit it now. If anyone wants to try using it, I can share my working copy where the fixes are present. From: RogerV <roger.var...@googlemail.com> To: user@struts.apache.org Date: 16-09-2010 18:34 Subject: Re: Struts 2, Session Management and "WorkFlow". RogerV wrote: > > > > Dave Newton-6 wrote: >> >> Correct--the essence of implementation is just a "dual-layer" context >> with >> the additional key passed back and forth (I assume for every request). >> > > Hi Dave, > > Doesn't seem too complicated to implement :) - but given this > conversation from Jan 2009 > http://old.nabble.com/Struts-2-session-problem-td21513305i40.html and this > from November 2006 > http://old.nabble.com/-s2--Multiple-Session-Conversations-Using-Same-Action-td7364935.html#a7364935 , > it would appear that it either proved too complicated or there was > insufficient "push". Any insights? > > Regards > > > Doh! This wouldn't be the raison d'etre for the Scope plugin by any chance? -- View this message in context: http://old.nabble.com/Struts-2%2C-Session-Management-and-%22WorkFlow%22.-tp29726121p29728230.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
