Michael Jouravlev wrote:
On a side note, I cannot get why storing data in an action form is
considered wrong, while directly accessing session is OK. I think
Well it is quite the opposite in JSF... using the session is
sort of a secure source of getting heavy beating (which is half right
but too extreme), while the so called backend beans are combined
controller/nmodel objects which basically are kept over all phases
of the rendering cycle.
The no use of session if possible results in such things like
x:saveState which serializes everything to pass data over the
cycle boundaries without having to pass parameters.
An interesting approach if you ask me, but puts too much emphasis on the
serialisation mechanism, a mixed form would be better, where you can
chose one way or the other.
quite opposite. I prefer to stick data related to an action, into
action form. It is more controlled, more visible, and then I can
simply remove one action form object from the session to clear the
whole tree.
Well a combind form, controller approach is closer to classical UIs than
the way struts does it. Although I can see the logic behind the approach
of struts in a http context, it is sort of confusing.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
