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

Norman Richards (JIRA) jira-events at lists.jboss.org
Wed Jun 11 14:55:29 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=comments#action_12416565 ] 
            
Norman Richards commented on JBSEAM-2186:
-----------------------------------------

I'm not sure I follow this.  Can you reproduce this without the login-required="true"

> RichFaces loses skin with login-required="true" in pages.xml
> ------------------------------------------------------------
>
>                 Key: JBSEAM-2186
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2186
>             Project: 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.CR1
>
>
> 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