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

Tue Feb 9 04:49:19 EST 2010

    [ https://jira.jboss.org/jira/browse/JBSEAM-4229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12511222#action_12511222 ] 

Damian Harvey commented on JBSEAM-4229:
---------------------------------------

I can reliably reproduce this issue under Seam 2.1.2.

If your pages.xml has login-required="true"

and in your component.xml you have enabled caching; eg:
<web:ajax4jsf-filter enable-cache="true" /> 

> RichFaces loses skin with login-required="true" in pages.xml
> ------------------------------------------------------------
>
>                 Key: JBSEAM-4229
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4229
>             Project: Seam
>          Issue Type: Bug
>    Affects Versions: 2.1.2.CR2
>         Environment: Seam 2.1.1.GA on JBoss 5.0.0.GA. 
>            Reporter: Moritz Winter
>
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira