Bug 822214 - Richfaces kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP Status 500
Summary: Richfaces kitchensink archetype - accessing wrong facelet is held in session ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Examples, RichFaces
Version: 2.0.0.ER5
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: CR1
: 2.1.0
Assignee: Brian Leathem
QA Contact: Pavol Pitonak
URL:
Whiteboard: rf-kitchensink
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-16 16:12 UTC by Juraj Huska
Modified: 2014-09-30 23:37 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-30 15:33:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RF-12254 0 Minor Closed kitchensink archetype - accessing wrong facelet is held in session and consequently accessing a correct one causes HTTP ... 2012-12-19 18:14:06 UTC

Description Juraj Huska 2012-05-16 16:12:42 UTC
Description of problem:
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,

public void setLocation(String location) {
        this.location = location;
        this.page = String.format("/mobile/%s.xhtml", location);
}
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.

Version-Release number of selected component (if applicable):
Richfaces 4.2.1.Final

Steps to Reproduce:
1. load application from generated kitchensink archetype
2 go to List Members view
3. you should be on the URL: http://your.ip.address:8080/contextRoot/#list
4. go to the wrong URL http://your.ip.address:8080/contextRoot/#lis
5. go to the correct URL http://your.ip.address:8080/contextRoot/ and see that 500 is returned

Comment 2 JBoss JIRA Server 2012-10-30 23:36:28 UTC
Brian Leathem <bleathem> updated the status of jira RF-12254 to Resolved

Comment 3 JBoss JIRA Server 2012-10-30 23:36:28 UTC
Brian Leathem <bleathem> made a comment on jira RF-12254

Added a resource look-up to the page bean to make sure the view exists

Comment 5 Karel Piwko 2012-11-30 15:33:45 UTC
Distributed as a part of WFK 2.1.0.GA release.

Comment 6 JBoss JIRA Server 2012-12-19 18:14:06 UTC
Juraj Húska <jhuska> updated the status of jira RF-12254 to Closed


Note You need to log in before you can comment on or make changes to this bug.