Unfortunately there are quite a few issues with doing that.
(See my post: How to overcome server amnesia with session scope? [was: Is
Struts architecture a disadvantage?])

-----Original Message-----
From: Claudio Parnenzini [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 16:37
To: Struts Users Mailing List
Subject: RE: Is Struts architecture a disadvantage?


You will not have heavily load if you put the ActionForm into the request
scope.

-----Message d'origine-----
De : Yaman Kumar [mailto:[EMAIL PROTECTED]]
Envoy� : vendredi, 7. juin 2002 08:51
� : Struts Users Mailing List
Objet : Is Struts architecture a disadvantage?


MessageHi,
I have a question regarding struts architecture, As the Html form and
its
validation has been moved and
implemented at server side ( a ActionForm ), once any validation error
encounters that  is shown
in the same page from which this request is generated ( this is very
impressing), but the page
can't retain its old information other than form information.

Case:
An action class bound data into request scope with 3 different attribute
names and forwarding to x.jsp which has
got a form (XFORM) too. In x.jsp it received 3 different attributes and
shown data in tabular format , when
user submits this form to different action this form bean will be
validated
and if any errors encountered x.jsp
page would be shown back to user, at this time user can't see the data
that
is shown tabular format.
As request is new it can't hold the previous state, this compels the
struts
users to keep this data(3 attributes)in session scope so when user comes
back he could see the error with the data too. In a big web application
if
we keep data
in session scope the server/application become heavily loaded.

Don't you think this is disadvantage of keeping /validating the formbean
at
server side. But I'm sure there are more and more advantages over this
disadvantage.

Please let me know if any better way to solve above problem and forgive
me
to  understand this as a disadvantage
of struts architecture.

Thanks
yaman


--
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]>

Reply via email to