[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
[
https://issues.jboss.org/browse/RF-12254?page=com.atlassian.jira.plugin.s...
]
RH Bugzilla Integration commented on RF-12254:
----------------------------------------------
Juraj Huska <jhuska(a)redhat.com> made a comment on [bug
822214|https://bugzilla.redhat.com/show_bug.cgi?id=822214]
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
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
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira