You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Ki...@OneAmerica.com on 2014/09/04 21:51:02 UTC
SERIALIZE_STATE_IN_SESSION - What does it do?
We have a custom address tag that seems to behave differently based on
whether SERIIALIZE_STATE_IN_SESSION is set to true or false.
When it is set to true, the values entered by the user on the page never
make it to the managed bean. When it is set to false, the values
entered do make it to the managed bean. Any idea why changing the value
of this parameter would impact the property being updated
in the managed bean or not? Our applications are running in a clustered
environment, so we are thinking that SERIALIZE_STATE_IN_SESSION
should be set to true so things will failover correctly. Is that
correct?
Thanks
This e-mail message is intended only for the use of the individual or entity to
which the transmission is addressed. Any interception may be a violation of
law. If you are not the intended recipient, any dissemination, distribution or
copying of this e-mail is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the document.
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Posted by Leonardo Uribe <lu...@gmail.com>.
Hi
2014-09-04 16:23 GMT-05:00 <Ki...@oneamerica.com>:
> Leonardo,
>
> Thanks for the response. We don't have any view scoped managed beans. The
> bean is session scoped.
> It does implement Serializable. We recently migrated from MyFaces 1,1,4 to
> MyFaces 2.1.13. This worked fine before, but isn't working
> now, if SERIALIZE_STATE_IN_SESSION is set to true. We are still using
> JSPs, not Facelets. I've stepped through the code several times and
> haven't
> discovered the issue yet.
>
>
Many things has happened since 1.1. JSP was deprecated in JSF 2.0 and the
suggested way is migrate JSP views into Facelets. Some component libraries
for JSF 2.0 deprecate JSP too. My suggestion is you could try first move
your application to MyFaces 1.2.12 (JSF 1.2) (change from JSF 1.1 EL to
Unified EL) and then convert your JSP views into Facelets and try 2.1.13.
regards,
Leonardo Uribe
>
>
>
> Kim Calvin
> Sr Systems Consultant - Web Solutions
> OneAmerica
> P.O. Box 368
> Indianapolis, IN 46206
> Phone: (317) 285-2401
> Fax: (317) 285-7696
> Kim.Calvin@oneamerica.com
>
> OneAmerica companies:
> AUL | State Life | OneAmerica Securities |
> McCready and Keene | PML | AUL RMS
>
>
>
> From: Leonardo Uribe <lu...@gmail.com>
> To: MyFaces Discussion <us...@myfaces.apache.org>,
> Date: 09/04/2014 04:19 PM
> Subject: Re: SERIALIZE_STATE_IN_SESSION - What does it do?
>
>
>
> Hi
>
> Check if your view scope managed beans implements Serializable interface.
> When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope
> beans, and if you have not marked them as Serializable, the values will
> get
> lost. In a cluster, it is possible to find configurations where a session
> is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with
> that scenario, to avoid exceptions later when the session is deserialized.
>
> regards,
>
> Leonardo Uribe
>
>
> 2014-09-04 14:51 GMT-05:00 <Ki...@oneamerica.com>:
>
> > We have a custom address tag that seems to behave differently based on
> > whether SERIIALIZE_STATE_IN_SESSION is set to true or false.
> > When it is set to true, the values entered by the user on the page never
> > make it to the managed bean. When it is set to false, the values
> > entered do make it to the managed bean. Any idea why changing the
> value
> > of this parameter would impact the property being updated
> > in the managed bean or not? Our applications are running in a
> clustered
> > environment, so we are thinking that SERIALIZE_STATE_IN_SESSION
> > should be set to true so things will failover correctly. Is that
> > correct?
> >
> > Thanks
> >
> >
> >
> >
> > This e-mail message is intended only for the use of the individual or
> > entity to
> > which the transmission is addressed. Any interception may be a violation
> of
> > law. If you are not the intended recipient, any dissemination,
> > distribution or
> > copying of this e-mail is strictly prohibited. If you are not the
> intended
> > recipient, please contact the sender by reply e-mail and destroy all
> > copies of
> > the document.
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
>
> This e-mail message is intended only for the use of the individual or
> entity to
> which the transmission is addressed. Any interception may be a violation of
> law. If you are not the intended recipient, any dissemination,
> distribution or
> copying of this e-mail is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of
> the document.
>
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Posted by Ki...@OneAmerica.com.
Leonardo,
Thanks for the response. We don't have any view scoped managed beans. The
bean is session scoped.
It does implement Serializable. We recently migrated from MyFaces 1,1,4 to
MyFaces 2.1.13. This worked fine before, but isn't working
now, if SERIALIZE_STATE_IN_SESSION is set to true. We are still using
JSPs, not Facelets. I've stepped through the code several times and
haven't
discovered the issue yet.
Kim Calvin
Sr Systems Consultant - Web Solutions
OneAmerica
P.O. Box 368
Indianapolis, IN 46206
Phone: (317) 285-2401
Fax: (317) 285-7696
Kim.Calvin@oneamerica.com
OneAmerica companies:
AUL | State Life | OneAmerica Securities |
McCready and Keene | PML | AUL RMS
From: Leonardo Uribe <lu...@gmail.com>
To: MyFaces Discussion <us...@myfaces.apache.org>,
Date: 09/04/2014 04:19 PM
Subject: Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Hi
Check if your view scope managed beans implements Serializable interface.
When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope
beans, and if you have not marked them as Serializable, the values will
get
lost. In a cluster, it is possible to find configurations where a session
is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with
that scenario, to avoid exceptions later when the session is deserialized.
regards,
Leonardo Uribe
2014-09-04 14:51 GMT-05:00 <Ki...@oneamerica.com>:
> We have a custom address tag that seems to behave differently based on
> whether SERIIALIZE_STATE_IN_SESSION is set to true or false.
> When it is set to true, the values entered by the user on the page never
> make it to the managed bean. When it is set to false, the values
> entered do make it to the managed bean. Any idea why changing the
value
> of this parameter would impact the property being updated
> in the managed bean or not? Our applications are running in a
clustered
> environment, so we are thinking that SERIALIZE_STATE_IN_SESSION
> should be set to true so things will failover correctly. Is that
> correct?
>
> Thanks
>
>
>
>
> This e-mail message is intended only for the use of the individual or
> entity to
> which the transmission is addressed. Any interception may be a violation
of
> law. If you are not the intended recipient, any dissemination,
> distribution or
> copying of this e-mail is strictly prohibited. If you are not the
intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of
> the document.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
This e-mail message is intended only for the use of the individual or entity to
which the transmission is addressed. Any interception may be a violation of
law. If you are not the intended recipient, any dissemination, distribution or
copying of this e-mail is strictly prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the document.
Re: SERIALIZE_STATE_IN_SESSION - What does it do?
Posted by Leonardo Uribe <lu...@gmail.com>.
Hi
Check if your view scope managed beans implements Serializable interface.
When SERIALIZE_STATE_IN_SESSION, it forces serialization of all view scope
beans, and if you have not marked them as Serializable, the values will get
lost. In a cluster, it is possible to find configurations where a session
is serialized and deserialized, so SERIALIZE_STATE_IN_SESSION help with
that scenario, to avoid exceptions later when the session is deserialized.
regards,
Leonardo Uribe
2014-09-04 14:51 GMT-05:00 <Ki...@oneamerica.com>:
> We have a custom address tag that seems to behave differently based on
> whether SERIIALIZE_STATE_IN_SESSION is set to true or false.
> When it is set to true, the values entered by the user on the page never
> make it to the managed bean. When it is set to false, the values
> entered do make it to the managed bean. Any idea why changing the value
> of this parameter would impact the property being updated
> in the managed bean or not? Our applications are running in a clustered
> environment, so we are thinking that SERIALIZE_STATE_IN_SESSION
> should be set to true so things will failover correctly. Is that
> correct?
>
> Thanks
>
>
>
>
> This e-mail message is intended only for the use of the individual or
> entity to
> which the transmission is addressed. Any interception may be a violation of
> law. If you are not the intended recipient, any dissemination,
> distribution or
> copying of this e-mail is strictly prohibited. If you are not the intended
> recipient, please contact the sender by reply e-mail and destroy all
> copies of
> the document.