Re: scope for form beans

2002-01-09 Thread Shengmeng Liu

Hi,
Essentially, the form bean is the model for the web tier.
It's state can be associated with a certain request, in this case,
it will be stored as a request-scope attribute. If it's state is 
associated with a certain user/session, then it will be stored as
a session-scope attribute.
Categorizing state into different scopes, namely request, session and
context will best reflect its nature and allow the servlet container to
manage(instantiate/use/destroy) accordingly. Form bean is just one of
this kind of state.

Hope this helps,
Shengmeng Liu

- Original Message - 
From: "Chen, Yong" <[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
Sent: Tuesday, January 08, 2002 11:43 PM
Subject: RE: scope for form beans


> what if one of your forms is never used in a session?
> and with session level bean, how would you know the form bean doesn't
> contain old data? form is request based not session based. you can certainly
> store some info. from the form in the session.
> 
> yc
> 
> 
> -Original Message-
> From: Kuntz Peter, NY [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 08, 2002 7:29 AM
> To: [EMAIL PROTECTED]
> Subject: scope for form beans
> 
> 
> Hi,
> 
> what are the motivations for having a request or session scoped form bean.
> As far as I could see in the struts source code a request scoped form bean
> is instantiated newly for every request. What are the reasons for that. Why
> shouldn't a form bean always exist during the time the session exists?
> 
> peter
> DISCLAIMER: The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee.  Access to this
> message by anyone else is unauthorised.  If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it, is prohibited and may be
> unlawful.  Please immediately contact the sender if you have received this
> message in error. Thank you
> 
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
> 
> --
> To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
> 




Re: scope for form beans

2002-01-08 Thread Muralidhar_BR



Hi
does this also mean the form bean goes null when the session gets timedout?
Regards,
Murali




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.Kindlesystems.com
**

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




Re: scope for form beans

2002-01-08 Thread Freek Segers

Hi,

I'm using a session scope Form bean in a wizard like interface. Because the
Form has session scope the user can go back to any step in the wizard and
find his previously filled in values.

Greetings,

Freek Segers

on 08-01-2002 14:28 you wrote:

> Hi,
> 
> what are the motivations for having a request or session scoped form bean.
> As far as I could see in the struts source code a request scoped form bean
> is instantiated newly for every request. What are the reasons for that. Why
> shouldn't a form bean always exist during the time the session exists?
> 


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




RE: scope for form beans

2002-01-08 Thread Chen, Yong

what if one of your forms is never used in a session?
and with session level bean, how would you know the form bean doesn't
contain old data? form is request based not session based. you can certainly
store some info. from the form in the session.

yc


-Original Message-
From: Kuntz Peter, NY [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 08, 2002 7:29 AM
To: [EMAIL PROTECTED]
Subject: scope for form beans


Hi,

what are the motivations for having a request or session scoped form bean.
As far as I could see in the struts source code a request scoped form bean
is instantiated newly for every request. What are the reasons for that. Why
shouldn't a form bean always exist during the time the session exists?

peter
DISCLAIMER: The information in this message is confidential and may be
legally privileged. It is intended solely for the addressee.  Access to this
message by anyone else is unauthorised.  If you are not the intended
recipient, any disclosure, copying, or distribution of the message, or any
action or omission taken by you in reliance on it, is prohibited and may be
unlawful.  Please immediately contact the sender if you have received this
message in error. Thank you

--
To unsubscribe, e-mail:

For additional commands, e-mail:


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