You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Michael Heinen <mh...@recommind.com> on 2008/03/10 18:39:35 UTC
t:saveState and richfaces ?
I am facing a problem with t:saveState which could be caused by
richfaces/ajax4jsf (but not sure about it)
The saved component is still "living" after leaving and revisiting a
page.
I defined a managed bean in request scope:
<managed-bean-name>WorkflowController</managed-bean-name>
<managed-bean-scope>request</managed-bean-scope>
It is saved via:
<t:saveState id="savedWorkflowController"
value="#{WorkflowController}"/>
If I enter the page the first time then the Constructor of
WorkflowController is called. If I now leave the page and re-enter it I
expect that a new instance is created, but it isn't.
I am sure that this feature was working well in the past.
An older version of my workspace with ajax4js4 1.1.0 is running fine.
Unfortunately I can't go back to this version in my current workspace
due to incompatibilities.
Any ideas how to isolate this problem quickly?
My enviroment:
myFaces 1.1.5
tomahawk 1.1.5 snapshot
richfaces-ui-3.1.4 GA
tiles and jsps (no facelets)
server-side state saving
RE: t:saveState and richfaces ?
Posted by Michael Heinen <mh...@recommind.com>.
Thanks Geoff.
I posted this also to the richfaces list: http://jboss.com/index.html?module=bb&op=viewtopic&t=131586
There is also an issue in their jira: http://jira.jboss.com/jira/browse/RF-1519
Michael
-----Original Message-----
From: Geoff Longo [mailto:gmlongo@gmail.com]
Sent: Montag, 10. März 2008 20:37
To: MyFaces Discussion
Subject: Re: t:saveState and richfaces ?
I think this might have been addressed in the latest RichFaces
development builds (3.2?) but I haven't been able to confirm. Has
anybody gotten around this issue?
On Mon, Mar 10, 2008 at 1:39 PM, Michael Heinen <mh...@recommind.com> wrote:
>
>
>
>
> I am facing a problem with t:saveState which could be caused by
> richfaces/ajax4jsf (but not sure about it)
>
> The saved component is still "living" after leaving and revisiting a page.
>
>
>
> I defined a managed bean in request scope:
>
> <managed-bean-name>WorkflowController</managed-bean-name>
>
> <managed-bean-scope>request</managed-bean-scope>
>
>
>
> It is saved via:
>
> <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/>
>
>
>
> If I enter the page the first time then the Constructor of
> WorkflowController is called. If I now leave the page and re-enter it I
> expect that a new instance is created, but it isn't.
>
>
>
> I am sure that this feature was working well in the past.
>
> An older version of my workspace with ajax4js4 1.1.0 is running fine.
> Unfortunately I can't go back to this version in my current workspace due to
> incompatibilities.
>
>
>
> Any ideas how to isolate this problem quickly?
>
>
>
> My enviroment:
>
> myFaces 1.1.5
>
> tomahawk 1.1.5 snapshot
>
> richfaces-ui-3.1.4 GA
>
> tiles and jsps (no facelets)
>
> server-side state saving
>
>
Re: t:saveState and richfaces ?
Posted by Geoff Longo <gm...@gmail.com>.
I think this might have been addressed in the latest RichFaces
development builds (3.2?) but I haven't been able to confirm. Has
anybody gotten around this issue?
On Mon, Mar 10, 2008 at 1:39 PM, Michael Heinen <mh...@recommind.com> wrote:
>
>
>
>
> I am facing a problem with t:saveState which could be caused by
> richfaces/ajax4jsf (but not sure about it)
>
> The saved component is still "living" after leaving and revisiting a page.
>
>
>
> I defined a managed bean in request scope:
>
> <managed-bean-name>WorkflowController</managed-bean-name>
>
> <managed-bean-scope>request</managed-bean-scope>
>
>
>
> It is saved via:
>
> <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/>
>
>
>
> If I enter the page the first time then the Constructor of
> WorkflowController is called. If I now leave the page and re-enter it I
> expect that a new instance is created, but it isn't.
>
>
>
> I am sure that this feature was working well in the past.
>
> An older version of my workspace with ajax4js4 1.1.0 is running fine.
> Unfortunately I can't go back to this version in my current workspace due to
> incompatibilities.
>
>
>
> Any ideas how to isolate this problem quickly?
>
>
>
> My enviroment:
>
> myFaces 1.1.5
>
> tomahawk 1.1.5 snapshot
>
> richfaces-ui-3.1.4 GA
>
> tiles and jsps (no facelets)
>
> server-side state saving
>
>
RE: t:saveState and richfaces ?
Posted by Michael Heinen <mh...@recommind.com>.
I noticed today that this bug occurs only if I use outputLinks.
Beans are re-instantiated as expected if I execute commandLinks or commandButtons.
They live on if I execute simple outputLinks!
The same happens if I use a4j:keepALive instead of t:saveState.
Any ideas ?
I am still not sure whether this is an a4j or a myFaces issue!
Michael
-----Original Message-----
From: Michael Heinen [mailto:mhn@recommind.com]
Sent: Freitag, 14. März 2008 12:02
To: MyFaces Discussion
Subject: RE: t:saveState and richfaces ?
Thanks Ognjen.
Hmm, I have this issue with 3.1.4 GA but I can't upgrade to myFaces 1.2.2 or any other JSF 1.2 impl.
This means it is a richfaces issue in combination with a myfaces 1.1.X version only.
I didn't get any feedback from the richfaces people so far.
Michael
-----Original Message-----
From: Ognjen Blagojevic [mailto:ognjen@etf.bg.ac.yu]
Sent: Freitag, 14. März 2008 11:33
To: MyFaces Discussion
Subject: Re: t:saveState and richfaces ?
I had the same problem, easy reproducible with
MyFaces 1.2.2, Tomahawk 1.1.6 and RichFaces 3.1.2 SP1.
I switched to RichFaces 3.1.4 GA, and now it works fine.
Regards,
Ognjen
Michael Heinen wrote:
> I am facing a problem with t:saveState which could be caused by
> richfaces/ajax4jsf (but not sure about it)
>
> The saved component is still "living" after leaving and revisiting a page.
>
>
>
> I defined a managed bean in request scope:
>
> <managed-bean-name>WorkflowController</managed-bean-name>
>
> <managed-bean-scope>request</managed-bean-scope>
>
>
>
> It is saved via:
>
> <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/>
>
>
>
> If I enter the page the first time then the Constructor of
> WorkflowController is called. If I now leave the page and re-enter it I
> expect that a new instance is created, but it isn't.
>
>
>
> I am sure that this feature was working well in the past.
>
> An older version of my workspace with ajax4js4 1.1.0 is running fine.
> Unfortunately I can't go back to this version in my current workspace
> due to incompatibilities.
>
>
>
> Any ideas how to isolate this problem quickly?
>
>
>
> My enviroment:
>
> myFaces 1.1.5
>
> tomahawk 1.1.5 snapshot
>
> richfaces-ui-3.1.4 GA
>
> tiles and jsps (no facelets)
>
> server-side state saving
>
>
>
RE: t:saveState and richfaces ?
Posted by Michael Heinen <mh...@recommind.com>.
Thanks Ognjen.
Hmm, I have this issue with 3.1.4 GA but I can't upgrade to myFaces 1.2.2 or any other JSF 1.2 impl.
This means it is a richfaces issue in combination with a myfaces 1.1.X version only.
I didn't get any feedback from the richfaces people so far.
Michael
-----Original Message-----
From: Ognjen Blagojevic [mailto:ognjen@etf.bg.ac.yu]
Sent: Freitag, 14. März 2008 11:33
To: MyFaces Discussion
Subject: Re: t:saveState and richfaces ?
I had the same problem, easy reproducible with
MyFaces 1.2.2, Tomahawk 1.1.6 and RichFaces 3.1.2 SP1.
I switched to RichFaces 3.1.4 GA, and now it works fine.
Regards,
Ognjen
Michael Heinen wrote:
> I am facing a problem with t:saveState which could be caused by
> richfaces/ajax4jsf (but not sure about it)
>
> The saved component is still "living" after leaving and revisiting a page.
>
>
>
> I defined a managed bean in request scope:
>
> <managed-bean-name>WorkflowController</managed-bean-name>
>
> <managed-bean-scope>request</managed-bean-scope>
>
>
>
> It is saved via:
>
> <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/>
>
>
>
> If I enter the page the first time then the Constructor of
> WorkflowController is called. If I now leave the page and re-enter it I
> expect that a new instance is created, but it isn't.
>
>
>
> I am sure that this feature was working well in the past.
>
> An older version of my workspace with ajax4js4 1.1.0 is running fine.
> Unfortunately I can't go back to this version in my current workspace
> due to incompatibilities.
>
>
>
> Any ideas how to isolate this problem quickly?
>
>
>
> My enviroment:
>
> myFaces 1.1.5
>
> tomahawk 1.1.5 snapshot
>
> richfaces-ui-3.1.4 GA
>
> tiles and jsps (no facelets)
>
> server-side state saving
>
>
>
Re: t:saveState and richfaces ?
Posted by Ognjen Blagojevic <og...@etf.bg.ac.yu>.
I had the same problem, easy reproducible with
MyFaces 1.2.2, Tomahawk 1.1.6 and RichFaces 3.1.2 SP1.
I switched to RichFaces 3.1.4 GA, and now it works fine.
Regards,
Ognjen
Michael Heinen wrote:
> I am facing a problem with t:saveState which could be caused by
> richfaces/ajax4jsf (but not sure about it)
>
> The saved component is still "living" after leaving and revisiting a page.
>
>
>
> I defined a managed bean in request scope:
>
> <managed-bean-name>WorkflowController</managed-bean-name>
>
> <managed-bean-scope>request</managed-bean-scope>
>
>
>
> It is saved via:
>
> <t:saveState id="savedWorkflowController" value="#{WorkflowController}"/>
>
>
>
> If I enter the page the first time then the Constructor of
> WorkflowController is called. If I now leave the page and re-enter it I
> expect that a new instance is created, but it isn't.
>
>
>
> I am sure that this feature was working well in the past.
>
> An older version of my workspace with ajax4js4 1.1.0 is running fine.
> Unfortunately I can't go back to this version in my current workspace
> due to incompatibilities.
>
>
>
> Any ideas how to isolate this problem quickly?
>
>
>
> My enviroment:
>
> myFaces 1.1.5
>
> tomahawk 1.1.5 snapshot
>
> richfaces-ui-3.1.4 GA
>
> tiles and jsps (no facelets)
>
> server-side state saving
>
>
>