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

[Norman Richards (JIRA)]

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

Norman Richards closed JBSEAM-2186.
-----------------------------------

    Resolution: Done
      Assignee: Norman Richards  (was: Pete Muir)

I'm going to close this.  The workaround is obvious, and the fix is covered by other issues.  It's likely that any changes in this regard will be limited to seam 2.1.

> 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: Norman Richards
>             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