CONNER, BRENDAN (SBCSI) wrote:
When using Struts, we built a framework that used an xml file to specify
which actions used which beans, and then, upon execution of each
request, our framework automatically deleted from the Session those
beans that were not in the list for the action being invoked on that
request. That was our "conversation."
Sounds pretty much like many existing dialog systems, but on an easier
scale.
I think everybody has tried a solution one way or the other, because
this is a constant problem open for years and never been fully addressed
to everybodies satisfaction.
Most people probably are happy enough with pushing the data into the
session and keep the booktracking manually.
(which works but is nasty because of possible mem leaks)
Another interesting approach which I thought about on the struts side
for this problem was sort of a similar mechanism like x:saveState,
you probably can serialize a bean itself into the form
and traverse the entire date via a hidden field directly serialized into
the form.
I'm anxious to try out <x:saveState> to see how it compares....
One of the most elegant approaches I have seen up today to solve this
nasty issue, because it does not push yet another set of config files
upon the implementor. I just wonder if the implementor of this thing
ever thought about using his component for scoping, on general beans ;-)
Werner
