]
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
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: