[richfaces-issues] [JBoss JIRA] (RF-12254) kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/RF-12254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731665#comment-12731665 ] 

RH Bugzilla Integration commented on RF-12254:
----------------------------------------------

Karel Piwko <kpiwko at redhat.com> changed the Status of [bug 822214|https://bugzilla.redhat.com/show_bug.cgi?id=822214] from NEW to ON_QA
                
> kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500 
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RF-12254
>                 URL: https://issues.jboss.org/browse/RF-12254
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: archetype, mobile
>    Affects Versions: 4.2.2.Final
>         Environment: project generated from kitchensink archetype
>            Reporter: Juraj Húska
>            Priority: Minor
>             Fix For: 4.2.4, 4.3.0.M3
>
>
> When accessing wrong facelet on mobile device and consequently the right application context, then the HTTP Status 500 is returned with error message, which can be viewed in the attached screenshot.
> It is caused because the {{PageBean}} hold the wrong part of the URL in the session,
> {code}
> public void setLocation(String location) {
>         this.location = location;
>         this.page = String.format("/mobile/%s.xhtml", location);
> }
> {code}
> Note that I have tried to change the scope of the PageBean to RequestScoped, but then the list with members what not updated with the new created ones. It is noticeable only on mobile devices, as on desktop there is only one view.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira