[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2186) RichFaces loses skin with login-required="true" in pages.xml
[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=comments#action_12398162 ]
Norman Richards commented on JBSEAM-2186:
-----------------------------------------
login-required="true" with view-id="*" causes RF to not be able to
find CSS files, which internally get mapped to /css/* URLs. The workarounds are to move
secure resources into a subdirectory and only restrict those files or to declare
login-required="true" for each view.
The resolution to JBSEAM-1009 may provide an alternative workaround.
RichFaces loses skin with login-required="true" in
pages.xml
------------------------------------------------------------
Key: JBSEAM-2186
URL: http://jira.jboss.com/jira/browse/JBSEAM-2186
Project: JBoss Seam
Issue Type: Bug
Affects Versions: 2.0.0.CR3
Environment: Seam CVS HEAD
Reporter: Justin C
Assigned To: Pete Muir
Fix For: 2.0.2.GA
To reproduce:
1) Create a new project via seam-gen.
2) Run ./seam new-entity and create a Foo entity (this gives you some CRUD screens)
2) Edit pages.xml and set attribute login-required="true" for the <page
view-id="*"> node.
3) Deploy the project and start the appserver.
4) Access the url for the app, this will direct to the login screen, to say that login is
required. Login, and access the CRUD screens.
5) Logout. Access a CRUD List screen from the menu. This may show a cached screen, so
refresh the page.
This directs to the login screen, but the RichFaces CSS skin is gone permanently.
--
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