[JBoss JIRA] Created: (RF-1519) <t:savestate> auto save request scope bean to session scope

[JBoss JIRA] Created: (RF-1255)...

[JBoss JIRA] Created: (RF-2202)...

shi long (JIRA)

Wednesday, 5 December 2007 Wed, 5 Dec '07

9:23 a.m.

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Components: doc Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Priority: Blocker when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Show replies by date

Nick Belaevski (JIRA)

Wednesday, 5 December Wed, 5 Dec

5:10 p.m.

New subject: [JBoss JIRA] Updated: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Nick Belaevski updated RF-1519: ------------------------------- Component/s: (was: doc) Fix Version/s: 3.2.0 Assignee: Anton Belevich Priority: Major (was: Blocker)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

Anton Belevich (JIRA)

Friday, 7 December Fri, 7 Dec

4:59 p.m.

New subject: [JBoss JIRA] Commented: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=comments#action_12391104 ] Anton Belevich commented on RF-1519: ------------------------------------ pls provide your pages

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Anton Belevich (JIRA)

Monday, 10 December Mon, 10 Dec

12:06 p.m.

New subject: [JBoss JIRA] Resolved: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Anton Belevich resolved RF-1519. -------------------------------- Fix Version/s: 3.1.3 Resolution: Cannot Reproduce Bug can't reproduce with trunk, branch 3.1.x, with 3.1.2 GA

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.1.3, 3.2.0 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Tsikhon Kuprevich (JIRA)

12:33 p.m.

New subject: [JBoss JIRA] Assigned: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Tsikhon Kuprevich reassigned RF-1519: ------------------------------------- Assignee: Aleksej Yanul (was: Anton Belevich)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Aleksej Yanul Fix For: 3.2.0, 3.1.3 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Tsikhon Kuprevich (JIRA)

12:33 p.m.

New subject: [JBoss JIRA] Assigned: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Tsikhon Kuprevich reassigned RF-1519: ------------------------------------- Assignee: Viktor Volkov (was: Aleksej Yanul)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Viktor Volkov Fix For: 3.2.0, 3.1.3 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Viktor Volkov (JIRA)

2:59 p.m.

New subject: [JBoss JIRA] Closed: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Viktor Volkov closed RF-1519. -----------------------------

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Viktor Volkov Fix For: 3.2.0, 3.1.3 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Anton Belevich (JIRA)

Wednesday, 26 December Wed, 26 Dec

4:40 p.m.

New subject: [JBoss JIRA] Reopened: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Anton Belevich reopened RF-1519: -------------------------------- Assignee: Anton Belevich (was: Viktor Volkov) user wrote: i test navigate from page1 to page2 through action ,it's ok. but in my enviorment ,i use iframe in page,left is navigate tree,right is iframe,user click left tree entry,iframe filled page content,if tree have two entry,when exchange page from tree entry,"error" appear. i think ,through ie's address ,i can simply test this question,first i type http://127.0.0.1:8090/test/testRichfacesTable1.faces,this backBean don't fetch data, fetch data in method doSearch,i click search button ,this action execute doSearch method,data is showing,second i type http://127.0.0.1:8090/test/testRichfacesTable2.faces ,when testRichfacesTable2.faces show,i type first page http://127.0.0.1:8090/test/testRichfacesTable1.faces,page data yet exists,in version 3.01,data don't appear ,because create new backBean. this is my quetion.

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0, 3.1.3 when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Anton Belevich (JIRA)

4:54 p.m.

New subject: [JBoss JIRA] Updated: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Anton Belevich updated RF-1519: ------------------------------- Attachment: richface question sourcecode.rar

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0, 3.1.3 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Nick Belaevski (JIRA)

Thursday, 27 December Thu, 27 Dec

2:27 p.m.

New subject: [JBoss JIRA] Updated: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Nick Belaevski updated RF-1519: ------------------------------- Fix Version/s: (was: 3.1.3)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

David Harris (JIRA)

Monday, 18 February Mon, 18 Feb

6:39 p.m.

New subject: [JBoss JIRA] Commented: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=comments#action_12399763 ] David Harris commented on RF-1519: ---------------------------------- I'm also seeing this in my development after switching from ajax4jsf to richfaces 3.1.5.GA. Prior to the switch my libraries included: ajax4jsf-1.1.1 myfaces-1.1.6 snapshots (from 10/31/07) tomahawk 1.1.7 snapshots (from (8/31/07) The only change I made was to replace ajax4jsf with richfaces, including new TLD references. New library list: richfaces-api-3.1.4.GA richfaces-impl-3.1.4.GA richfaces-ui-3.1.4.GA myfaces-1.1.6 snapshots (same ones) tomahawk 1.1.7 snapshots (same ones) Given 3 web pages, with identical t:savestate on pages 1 & 2, I should be able to navigate from iether page 1 or 2 to page 3 (away from the pages with the identical savestates) and then back to 1 or 2 and not see any data persist from the prior visit to 1 or 2. This was working correctly until the change to richfaces. I'm assuming the problem lies somewhere in the richfaces filter. Assuming this is the case, is there a way to workaround the problem without moving away from the Tomahawk savestate tags?

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

David Harris (JIRA)

7:56 p.m.

New subject: [JBoss JIRA] Commented: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=comments#action_12399773 ] David Harris commented on RF-1519: ---------------------------------- Short of downloading a snapshot of 3.2, I also tried using a4j:keepAlive and got the same results.

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Michael Heinen (JIRA)

Tuesday, 11 March Tue, 11 Mar

4:51 p.m.

New subject: [JBoss JIRA] Commented: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=comments#action_12402160 ] Michael Heinen commented on RF-1519: ------------------------------------ I am facing the same problem with richfaces 3.1.4. See user group for my case: http://jboss.com/index.html?module=bb&op=viewtopic&t=131586 I really need this fixed in 3.1.5 because I can't upgrade to richfaces 3.2.0 and jsf 1.2 in near future. This is a critical show stopper for me because my beans are not recreated with new data and stay somewhere in memory. Is it possible to fix it in 3.1.5 ?

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.0 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Nick Belaevski (JIRA)

Tuesday, 25 March Tue, 25 Mar

8:31 p.m.

New subject: [JBoss JIRA] Updated: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Nick Belaevski updated RF-1519: ------------------------------- Fix Version/s: 3.2.1 (was: 3.2.0)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.1 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Anton Belevich (JIRA)

Friday, 25 April Fri, 25 Apr

5:32 p.m.

New subject: [JBoss JIRA] Resolved: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Anton Belevich resolved RF-1519. -------------------------------- Resolution: Out of Date I'm trying using t:saveState with and without richfaces 3.2.1-SNAPSHOT behavior is the same (myfaces-1.2.2 and tomahawk 1.1.6)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Anton Belevich Fix For: 3.2.1 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

Tsikhon Kuprevich (JIRA)

Monday, 28 April Mon, 28 Apr

6:40 p.m.

New subject: [JBoss JIRA] Closed: (RF-1519) <t:savestate> auto save request scope bean to session scope

[ http://jira.jboss.com/jira/browse/RF-1519?page=all ] Tsikhon Kuprevich closed RF-1519. --------------------------------- Assignee: Tsikhon Kuprevich (was: Anton Belevich)

...

<t:savestate> auto save request scope bean to session scope ------------------------------------------------------------ Key: RF-1519 URL: http://jira.jboss.com/jira/browse/RF-1519 Project: RichFaces Issue Type: Bug Affects Versions: 3.1.0 Environment: windows xp sp2 tomcat 5.5 eclpise 3.2 jdk 1.5.08 myfaces1.5 facelets 1.1.13 Reporter: shi long Assigned To: Tsikhon Kuprevich Fix For: 3.2.1 Attachments: richface question sourcecode.rar when i use ajax4jsf1.1.10 and tomhawk 1.5,richfaces3.0 facelets 1.1.10 in developement,no problem. but when i upgrade to use richfaces3.1.0 later version, remain other package(tomhawk,facelets), for example: page1.xhtml <t:saveState value="bean1"></t:saveState> .... page2.xhtml <t:saveState value="bean2"></t:saveState> bean1 and bean2 both in request scope <managed-bean-scope>request </managed-bean-scope> in jsf page,when i in page1.jsf,bean1only create once,in page1.jsf,state saved . when i click into page2.jsf ,then ,click into page1.jsf,in richfaces3.0 ,old bean1 destroy,new bean1 create,but in richfaces3.1.0 ,old bean1 yet exist. so i guess richfaces3.1.0 auto transfer request scope bean to session. because from tomhawk documention,when bean not contain t:saveState in page ,request scope bean will destroy. sorry ,i don't master english language,i wish my question can read by others. thanks

5986

days inactive

6131

days old

richfaces-issues@lists.jboss.org

Manage subscription

15 comments

7 participants

tags (0)

participants (7)

Anton Belevich (JIRA)
David Harris (JIRA)
Michael Heinen (JIRA)
Nick Belaevski (JIRA)
shi long (JIRA)
Tsikhon Kuprevich (JIRA)
Viktor Volkov (JIRA)

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[JBoss JIRA] Created: (RF-1519) <t:savestate> auto save request scope bean to session scope