Is it worth building a mechanism for conversation scope, compared to the
complexity it introduces? I really dislike Spring Webflow with its conversation
scope, stringent encapsulation and storage of massive amounts of data in various
maps that locks away everything out of sight and makes it all taste like it's
been massively over-architected (and of course the practically insurmountable
learning curve)
Isn't it just easier to clean your variables out of the session manually when
done? I'm not trying to provoke another rant, it's just that I've suffered my
fair share of pain grappling with SWF and I find all justifications of its
complexity unwarranted.
Adam
Ray Clough on 24/02/08 02:23, wrote:
Thanks Jeromy. (usually my wife is the only one who notices my 'rants').
Jeromy Evans wrote:
Hi Ray,
I'm not sure, but check out Tom's new scope plugin as it may get you
part of the way there.
http://cwiki.apache.org/S2PLUGINS/scope-plugin.html
I was just reading one of your rants from August 07 that mentioned the
need to use ModelDriven's model across a conversation and think this
will be useful.
cheers,
Jeromy Evans
Ray Clough wrote:
JSF has a "ConversationScope" for extended series of requests/responses
dealing with the same topic, and usually the same data model. I'm
thinking
of writing an interceptor to simulate ConversationScope, and I'm
wondering
if this has not already been done, and if so, does anyone have details,
code, etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
