[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

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 Huska Priority: Minor Fix For: 4.2-Tracking, 4.3-Tracking 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.