[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=comments#action_12386305 ] Rolf Scherer commented on JBSEAM-2186: -------------------------------------- Hi all I have the same problem with Tomcat and embedded JBoss. @JBoss Seam Team: Great work! I love seam. Thank you -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=all ] Pete Muir updated JBSEAM-2186: ------------------------------ Environment: Seam CVS HEAD (was: Windows XP Professional, Java 1.6_03, JBoss 4.2.1) Description: 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. was: Create a new project via seam-gen. Generate some GRUD screens using generate-entities. Folow the seam-gen section in the Reference manual to do this. Edit pages.xml and set attribute login-required="true" for the <page view-id="*"> node. Do a seam explode and start the appserver. 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. Logout. Access a CRUD List screen from the menu. This will show a cached screen, not the login screen, as is expected. Refresh the screen from the browser. This directs to the login screen, but the RichFaces CSS skin is gone permamently. -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=all ] Norman Richards updated JBSEAM-2186: ------------------------------------ Fix Version/s: 2.0.1.GA (was: 2.0.1.CR1) -- 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

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

[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=all ] Norman Richards updated JBSEAM-2186: ------------------------------------ Fix Version/s: 2.0.2.GA (was: 2.0.1.CR2) -- 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

[ http://jira.jboss.com/jira/browse/JBSEAM-2186?page=comments#action_12398162 ] Norman Richards commented on JBSEAM-2186: ----------------------------------------- login-required="true" with view-id="*" causes RF to not be able to find CSS files, which internally get mapped to /css/* URLs. The workarounds are to move secure resources into a subdirectory and only restrict those files or to declare login-required="true" for each view. The resolution to JBSEAM-1009 may provide an alternative workaround. -- 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

[ 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 ;) -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-2186?page=com.atlassian.jira.pl... ] Moritz Winter commented on JBSEAM-2186: --------------------------------------- I can still reproduce this bug in Seam 2.1.1.GA on JBoss 5.0.0.GA. -- 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

[ https://jira.jboss.org/jira/browse/JBSEAM-2186?page=com.atlassian.jira.pl... ] Ilya German commented on JBSEAM-2186: ------------------------------------- It is reproducible in Seam 2.2.0.GA on Glassfish 2.1 as well -- 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

[ https://jira.jboss.org/browse/JBSEAM-2186?page=com.atlassian.jira.plugin.... ] Markos Fragkakis commented on JBSEAM-2186: ------------------------------------------ Also reproducible with Seam 2.2.1.CR1 and Weblogic 10.3.2 (11g) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira