On 11/11/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> On 11/11/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> > > > I added a "scenario" attribute to <action> element, and on each
> > > > request I am going to check session and to clean all form beans that
> > > > do not correspond to action's scenario ("scenario" attribute can
> > > > enlist several scenarios that action participates in). It would be
> > > > simpler to define scenario for <form-bean> themselves, but I think it
> > > > is easier for developer to think in terms of grouped actions, not
> > > > grouped forms.
> > >
> > > What happens if the user uses multiple windows?
> >
> > Nothing different from having multiple windows of a regular action
> > with session-scoped form. As long as action was called, form is used,
> > so no reason to dispose it. Or am I missing something?
> >
> Say I have Window A doing Scenario A. From there I open up another
> window and for whatever reason end up exploring Scenario B. If I
> submit either window, the one I didn't submit gets its session object
> hosed.
You are right, multiwindow thing breaks this idea. Maybe I could
introduce a flag "this formbean was submitted to" and remove only
submitted beans. Or flag "this form bean was processed"... Got a
better idea by any chance?
On 11/11/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> On 11/11/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> > It is hard for people to use a library
> > if it is not endorsed by Struts dev team, and even behaves in a
> > different manner? Even harder for them to make a mind shift.
>
> This is what I'm talking about. It's a matter of, uhm, "marketing".
> With Eclipse, they made it so using plugins is not only accepted, but
> expected. Why should it be different with Struts?
Actually, that would be a great new idea for Struts. I would support
it. Considering that 1.3 codebase should be much more flexible in
terms of plugins, that should work.
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
