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

[Tsikhon Kuprevich (JIRA)]

     [ 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

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