You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by JONATHAN PHILIP HOLLOWAY <jp...@aber.ac.uk> on 2003/01/10 17:10:26 UTC
Session Management
Hi everyone,
I'm wondering about the ways of managing sessions in Struts and wanted
to know out of these two ways which was the better way of doing things:
1. Storing things within the standard servlet session
2. Using a UserWrapper object and storing that within the session.
Is the second way more preformance intensive or not and which is best
practice?
Many thanks,
Jon Holloway.
*---------------------------------------------*
Jonathan Holloway,
Dept. Of Computer Science,
Aberystwyth University,
Ceredigion,
West Wales,
SY23 3DV.
07968 902140
http://users.aber.ac.uk/jph8
*---------------------------------------------*
Taglib with Dynaforms
Posted by LT Yield <lt...@yahoo.com>.
Hello all,
I just started using DynaValidatorForms for my form
beans instead of the traditional way. But I am having
problems retrieving the bean elements in
html/bean/logic tags. Do these tags support the
Dynaforms or do I need to alter the tags on my own to
do the appropriate getters and setters for dynaforms?
Any assistance would be greatly appreciated,
Lionel
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Session Management
Posted by Puneet Agarwal <pu...@rediffmail.com>.
Session Management is required to achieve persistence. there are two manner
in which persistence can be achieved.
1. storing the information in HTTP session (possibly in session scope)
2. Storing the information using stateful session beans.
You have to take the decision based on your application's performance
expectations.
The cleaner approach is to define the scope of form as "session" and storing
everything in formbeans, nowhere else.
some readonly information can be stored in application context also.
Well you may choose to store some information in stateful session beans and
some in formbeans (HTTP session) but I would not suggest to keep the scope
of formbeans as "request" unless the screen is totally stateless.
Regards
Puneet
----- Original Message -----
From: "JONATHAN PHILIP HOLLOWAY" <jp...@aber.ac.uk>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Friday, January 10, 2003 4:10 PM
Subject: Session Management
Hi everyone,
I'm wondering about the ways of managing sessions in Struts and wanted
to know out of these two ways which was the better way of doing things:
1. Storing things within the standard servlet session
2. Using a UserWrapper object and storing that within the session.
Is the second way more preformance intensive or not and which is best
practice?
Many thanks,
Jon Holloway.
*---------------------------------------------*
Jonathan Holloway,
Dept. Of Computer Science,
Aberystwyth University,
Ceredigion,
West Wales,
SY23 3DV.
07968 902140
http://users.aber.ac.uk/jph8
*---------------------------------------------*
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Session Management
Posted by Phil Steitz <ph...@steitz.com>.
Puneet Agarwal wrote:
> Session Management is required to achieve persistence. there are two manner
> in which persistence can be achieved.
>
> 1. storing the information in HTTP session (possibly in session scope)
> 2. Storing the information using stateful session beans.
You can also use hidden fields (basically client-side state management),
or application-managed durable storage (e.g RDBMS).
>
> You have to take the decision based on your application's performance
> expectations.
>
> The cleaner approach is to define the scope of form as "session" and storing
> everything in formbeans, nowhere else.
> some readonly information can be stored in application context also.
>
> Well you may choose to store some information in stateful session beans and
> some in formbeans (HTTP session) but I would not suggest to keep the scope
> of formbeans as "request" unless the screen is totally stateless.
Or unless the application has to scale to very large volumes, in which
case you want to be very careful about creating too many session-scoped
objects.
>
> Regards
> Puneet
>
> ----- Original Message -----
> From: "JONATHAN PHILIP HOLLOWAY" <jp...@aber.ac.uk>
> To: "Struts Users Mailing List" <st...@jakarta.apache.org>
> Sent: Friday, January 10, 2003 4:10 PM
> Subject: Session Management
>
>
> Hi everyone,
>
> I'm wondering about the ways of managing sessions in Struts and wanted
> to know out of these two ways which was the better way of doing things:
>
> 1. Storing things within the standard servlet session
>
> 2. Using a UserWrapper object and storing that within the session.
>
> Is the second way more preformance intensive or not and which is best
> practice?
>
> Many thanks,
> Jon Holloway.
>
> *---------------------------------------------*
> Jonathan Holloway,
> Dept. Of Computer Science,
> Aberystwyth University,
> Ceredigion,
> West Wales,
> SY23 3DV.
>
> 07968 902140
> http://users.aber.ac.uk/jph8
> *---------------------------------------------*
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JList
Posted by "Eric C. Hein" <gr...@mindspring.com>.
getItem() should take a String[].
----- Original Message -----
From: "Gus Delgado" <gd...@oceanobjects.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Friday, January 10, 2003 2:10 PM
Subject: Re: JList
> will the getItem() in the Form take a Collection as suppose of a String?
>
> Eric C. Hein wrote:
>
> ><html:select property="item" styleClass="select" multiple="true" >
> > <html:options collection="itemList" property="value"
> >labelProperty="label"/>
> ></html:select>
> >
> >----- Original Message -----
> >From: "Gus Delgado" <gd...@oceanobjects.com>
> >To: "Struts Users Mailing List" <st...@jakarta.apache.org>
> >Sent: Friday, January 10, 2003 12:31 PM
> >Subject: JList
> >
> >
> >
> >
> >>On Struts and jsp tags, what is the alternative to a JList. Where a user
> >>can select multiple items from that list?
> >>
> >>-thanks
> >>Gus
> >>
> >>
> >>
> >>--
> >>To unsubscribe, e-mail:
> >>
> >>
> ><ma...@jakarta.apache.org>
> >
> >
> >>For additional commands, e-mail:
> >>
> >>
> ><ma...@jakarta.apache.org>
> >
> >
> >
> >
> >--
> >To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> >For additional commands, e-mail:
<ma...@jakarta.apache.org>
> >
> >
> >.
> >
> >
> >
>
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JList
Posted by Gus Delgado <gd...@oceanobjects.com>.
will the getItem() in the Form take a Collection as suppose of a String?
Eric C. Hein wrote:
><html:select property="item" styleClass="select" multiple="true" >
> <html:options collection="itemList" property="value"
>labelProperty="label"/>
></html:select>
>
>----- Original Message -----
>From: "Gus Delgado" <gd...@oceanobjects.com>
>To: "Struts Users Mailing List" <st...@jakarta.apache.org>
>Sent: Friday, January 10, 2003 12:31 PM
>Subject: JList
>
>
>
>
>>On Struts and jsp tags, what is the alternative to a JList. Where a user
>>can select multiple items from that list?
>>
>>-thanks
>>Gus
>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>>For additional commands, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>.
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JList
Posted by Gus Delgado <gd...@oceanobjects.com>.
it works fine Thank you
Eric C. Hein wrote:
><html:select property="item" styleClass="select" multiple="true" >
> <html:options collection="itemList" property="value"
>labelProperty="label"/>
></html:select>
>
>----- Original Message -----
>From: "Gus Delgado" <gd...@oceanobjects.com>
>To: "Struts Users Mailing List" <st...@jakarta.apache.org>
>Sent: Friday, January 10, 2003 12:31 PM
>Subject: JList
>
>
>
>
>>On Struts and jsp tags, what is the alternative to a JList. Where a user
>>can select multiple items from that list?
>>
>>-thanks
>>Gus
>>
>>
>>
>>--
>>To unsubscribe, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>>For additional commands, e-mail:
>>
>>
><ma...@jakarta.apache.org>
>
>
>
>
>--
>To unsubscribe, e-mail: <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>.
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: JList
Posted by "Eric C. Hein" <gr...@mindspring.com>.
<html:select property="item" styleClass="select" multiple="true" >
<html:options collection="itemList" property="value"
labelProperty="label"/>
</html:select>
----- Original Message -----
From: "Gus Delgado" <gd...@oceanobjects.com>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Friday, January 10, 2003 12:31 PM
Subject: JList
> On Struts and jsp tags, what is the alternative to a JList. Where a user
> can select multiple items from that list?
>
> -thanks
> Gus
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
JList
Posted by Gus Delgado <gd...@oceanobjects.com>.
On Struts and jsp tags, what is the alternative to a JList. Where a user
can select multiple items from that list?
-thanks
Gus
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Session Management
Posted by Puneet Agarwal <pu...@rediffmail.com>.
Session Management is required to achieve persistence. there are two manner
in which persistence can be achieved.
1. storing the information in HTTP session (possibly in session scope)
2. Storing the information using stateful session beans.
You have to take the decision based on your application's performance
expectations.
The cleaner approach is to define the scope of form as "session" and storing
everything in formbeans, nowhere else.
some readonly information can be stored in application context also.
Well you may choose to store some information in stateful session beans and
some in formbeans (HTTP session) but I would not suggest to keep the scope
of formbeans as "request" unless the screen is totally stateless.
Regards
Puneet
----- Original Message -----
From: "JONATHAN PHILIP HOLLOWAY" <jp...@aber.ac.uk>
To: "Struts Users Mailing List" <st...@jakarta.apache.org>
Sent: Friday, January 10, 2003 4:10 PM
Subject: Session Management
Hi everyone,
I'm wondering about the ways of managing sessions in Struts and wanted
to know out of these two ways which was the better way of doing things:
1. Storing things within the standard servlet session
2. Using a UserWrapper object and storing that within the session.
Is the second way more preformance intensive or not and which is best
practice?
Many thanks,
Jon Holloway.
*---------------------------------------------*
Jonathan Holloway,
Dept. Of Computer Science,
Aberystwyth University,
Ceredigion,
West Wales,
SY23 3DV.
07968 902140
http://users.aber.ac.uk/jph8
*---------------------------------------------*
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>