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

[Thomas Modeneis (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=comments#action_12416511 ] 
            
Thomas Modeneis commented on JBSEAM-2186:
-----------------------------------------

i think we all want fix this bug.

in my investigation i think the problem occours when you stop jboss, update some souces 
and explode then into AS. then you type restart jboss and try to execute some old action on GET (/action.seam?name="Mary"&lastname="Jane") 
this command execute a old session, (and because login-required=true) many exceptions will occour at same time. 
(ViewExpiredException and NotLoggedInException) 
then seam block acess variables and can´t process loadImplicit jars of richFaces correctly.

so, now this is some fixed point:
after explode new sources and restart jboss, clean the argument list of action.seam? and try to execute them.
just NotLoggedInException will occours, and seam can process loadImplicit jars of richFaces correctly.

i tink we need prevent this on first action method nullabling all arguments from get, to prevent 
ViewExpiredException, im not sure about how many exceptions occours....but i belive this is the way.

Thank you guys for Seam, this framework changed my life ;) 

> 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