Rick Reumann wrote:
Michael Jouravlev wrote the following on 7/28/2005 4:30 PM:
Ahem, actually I am all in for sessions. I just don't see why it
storing stuff in an action form with session scope is universally
frowned upon, while sticking same stuff directly into session is OK
;-)
Most seem
On 7/28/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> There should be set of policies. For example, if you navigate to an
> action which is not part of any subsession (or scenario, I like this
> word), do you trash all existing scenarios or you keep them?
If you look at Spring Web Flow, you w
On 7/28/05, Rick Reumann <[EMAIL PROTECTED]> wrote:
> Michael Jouravlev wrote the following on 7/28/2005 6:48 PM:
>
> > Wizard should be handled by *one* action, then cleanup would be
> > simple. Have you found time to look at my stuff? ;-)
>
> Sorry Michael I have not:( Send me the link again.
What we have done is kept all forms in session as "form". That way if
the user jumps to another set of pages and discards halfway tru the
current process the "form" session variable just gets reused and we
don't have to worry too much about cleanup
Shekhar
On 7/28/05, Rick Reumann <[EMAIL PROTECT
Michael Jouravlev wrote the following on 7/28/2005 6:48 PM:
Wizard should be handled by *one* action, then cleanup would be
simple. Have you found time to look at my stuff? ;-)
Sorry Michael I have not:( Send me the link again.
But, that being said, where clean up becomes a problem is when th
On 7/28/05, Rick Reumann <[EMAIL PROTECTED]> wrote:
> Ed Griebel wrote the following on 7/28/2005 5:11 PM:
> > Rick-
> >
> > I'm faced with this same problem on a new project and have been
> > thinking along these same lines. What kind of issues have you run
> > into?
>
> I really haven't run into
Ed Griebel wrote the following on 7/28/2005 5:11 PM:
Rick-
I'm faced with this same problem on a new project and have been
thinking along these same lines. What kind of issues have you run
into?
I really haven't run into many problems when I use a Session based form
for a wizard approach. Si
On 7/28/05, Ed Griebel <[EMAIL PROTECTED]> wrote:
> Rick-
>
> I'm faced with this same problem on a new project and have been
> thinking along these same lines. What kind of issues have you run
> into?
I am interested too ;)
> The kind of things that I see being a problem is specifying
> which s
1) I use session-scoped ActionForms with "extra" fields plenty (in search
scenarios for example, where the form is for search, where the search is
related to a product, and where you want to hang on to the product details as
the search results change) and couldn't care less who "frowns upon it".
Rick-
I'm faced with this same problem on a new project and have been
thinking along these same lines. What kind of issues have you run
into? The kind of things that I see being a problem is specifying
which sets of actions are associated with what items in a session, and
which sets of actions are
Werner Punz wrote the following on 7/28/2005 11:46 AM:
There are some ways to handle this
a) You can dump anything into the session, which means you run into
memory problems in the long run.
I use this solution and have yet to run into any sort of memory
problems. Resources aren't 'that' exp
Michael Jouravlev wrote the following on 7/28/2005 4:30 PM:
Ahem, actually I am all in for sessions. I just don't see why it
storing stuff in an action form with session scope is universally
frowned upon, while sticking same stuff directly into session is OK
;-)
Most seem to frown on both scen
On 7/28/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> 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
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
On 7/28/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> Actually I was thinking also along the lines of having some kind of
> garbage collecting mechanism.
> I did something like that in JSF very easy (reprogrammed parts of the
> x:saveState)
> the trick was to push the object into the session with so
Werner Punz wrote:
I tried to move over a similar mechanism in Struts, but basically
failed due to time constraints, which I cannot resolve by technical
means ;-)
If you were Really Good you could. Probably not a pure software
solution, though, especially if any space-time distortion is invo
Michael Jouravlev wrote:
On 7/28/05, Werner Punz <[EMAIL PROTECTED]> wrote:
I after Wendy gave me the advice to rephrase the question I will try to
rephrase it.
Being new to struts, I want to know how people deal with data objects
which need a scope bigger than request but smaller than session
Michael Jouravlev wrote:
There are no standard ways to do this. Creating wizards myself, I was
thinking about some kind of garbage collector for session object. This
project: http://wfnm.sourceforge.net/ seems to have this feature. It
has some other features so I don't know can you pull out the
On 7/28/05, Werner Punz <[EMAIL PROTECTED]> wrote:
> I after Wendy gave me the advice to rephrase the question I will try to
> rephrase it.
>
> Being new to struts, I want to know how people deal with data objects
> which need a scope bigger than request but smaller than session.
There are no sta
I after Wendy gave me the advice to rephrase the question I will try to
rephrase it.
Being new to struts, I want to know how people deal with data objects
which need a scope bigger than request but smaller than session.
I will give an example, you have some kind of wizard interface with
myriad
Hi I am banging sort of my head here
I am sort of new to struts (due to project requirements), in every
webapp you often have the problem of having to pass complex objects over
a handful of forms.
In JSP you only have the option of pushing the object into the session
and fill the data by h
21 matches
Mail list logo
