[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2186) RichFaces loses skin with login-required="true" in pages.xml

Pete Muir (JIRA) jira-events at lists.jboss.org
Sat Jan 5 10:19:43 EST 2008

     [ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=all ]

Pete Muir closed JBSEAM-2186.

    Resolution: Cannot Reproduce Bug

I'm now unable to reproduce this in CVS since the upgrade to RichFaces 3.1.3.GA. If people can reproduce with Seam CVS and RichFaces 3.1.3.GA then please reopen the issue with new reproduction steps.

> 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.1.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


More information about the seam-issues mailing list