struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alayne Wartell" <>
Subject Re: "deferring" an action
Date Thu, 14 Nov 2002 18:48:54 GMT

As a matter of fact, our users are chained to their desks.
Ok, I'm lying. But your suggestion may have merit -- the form would be in
session scope but not for very long -- just long enough to be put there
when the user clicks a link, then saved, then it could go away.

But would you mind explaining how putting the form in session scope would
solve the issue at hand? In some nice clean struts-like way?
The issue being 1) click for action #1   ;   2) perform action #2;   3)
perform action #1
where actions 1 and 2 are arbitrary, not known ahead of time.

                                               To:       "Struts Users Mailing List" <>
                      "Brian Hickey"           cc:       (bcc: Alayne Wartell/Towers Perrin)
                      <bhickey@r-effect        Subject:  Re: "deferring" an action    
                      11/14/2002 01:21                                                   
                      Please respond to                                                  
                      "Struts Users                                                      
                      Mailing List"                                                      


Would a time requirement mess things up? If not, your actions could simply
place the forms into session scope.

Most of our clients don't spend all day at their machines, so 30 minutes or
so is too much of a constraint...

Just a wild thought :o)


----- Original Message -----
From: "Alayne Wartell" <>
To: <>
Sent: Thursday, November 14, 2002 12:25 PM
Subject: "deferring" an action

> This is something I haven't seen discussed before. Our web application
> a large, dynamically built tree in its own frame by which users navigate
> input screens. ( They can also click on menu options -- slightly
> but raises the same issue for us.) Data entry is freeform -- users can
> navigate anywhere at any time. So far, no big deal. The unusual part is,
> when a user finishes entering data on a screen, then clicks to go to
> another screen, we automatically save the screen they're leaving. In a
> sense, we have to defer the page load action to do a save action on the
> prior page. So we're trying to come up with a clean way to fit this into
> Struts.
> The sequence is:
> Click link -> save current page  -> respond with reassuring message in
> another frame (i.e. "screen has been saved") -> go to clicked link
> We haven't come up with any designs we like yet. One example of something
> we don't like:
> 1) user fills out form, call it currentPage
> 1) user clicks to go to
> 2) javascript puts "" in hidden field on currentPage, and
>        then initiates a submit of currentPage
> 3) submit to
> 3) action forwards to jsp with hidden form -- '' is the form
> action (also, javascript puts confirmation message in header frame)
> 4) immediately submit that form using javascript
> Ideas, anyone? (Sure, we could do away with the auto-save to make our app
> more webbish -- if it weren't a business requirement. Besides, it really
> nice for the users.)
> Thanks,
> Alayne
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message