[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml
7:16 a.m.
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
--
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
7:16 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml
[
https://jira.jboss.org/jira/browse/JBSEAM-4229?page=com.atlassian.jira.pl...
]
Moritz Winter updated JBSEAM-4229:
----------------------------------
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.
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
5:28 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml
[
https://jira.jboss.org/jira/browse/JBSEAM-4229?page=com.atlassian.jira.pl...
]
Moritz Winter commented on JBSEAM-4229:
---------------------------------------
Sorry I think i mistakely did report this issue because I think its related to a bug in
the sonatype m2e plugin for eclipse, which doesnt copy libs correctly
(https://issues.sonatype.org/browse/MNGECLIPSE-1117). If I copy the libs manually or do a
pure maven deployment this issue is gone, so for me you can close it. Don't know if
the other voter/watcher still has this issue.
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
3:49 a.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml
[
https://jira.jboss.org/jira/browse/JBSEAM-4229?page=com.atlassian.jira.pl...
]
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
1:02 p.m.
New subject: [JBoss JIRA] Commented: (JBSEAM-4229) RichFaces loses skin with login-required="true" in pages.xml
[
https://jira.jboss.org/jira/browse/JBSEAM-4229?page=com.atlassian.jira.pl...
]
Harry Bush commented on JBSEAM-4229:
------------------------------------
I can reliably repordue this issue with a global navigation rule and
login-required="true"
<?xml version="1.0" encoding="UTF-8"?>
<pages xmlns="http://jboss.com/products/seam/pages"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://jboss.com/products/seam/pages
http://jboss.com/products/seam/pages-2.1.xsd"
login-view-id="/portal/login.xhtml">
<page view-id="*" login-required="true" >
<navigation>
<rule if-outcome="com.expd.portal.launch">
<redirect url="#{launchURL.url}" />
</rule>
</navigation>
<navigation from-action="#{identity.login}">
<rule if="#{identity.loggedIn}">
<redirect view-id="/portal/landing.xhtml"/>
</rule>
</navigation>
</page>
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
5168
days inactive
5473
days old
4 comments
3 participants
participants (3)
-
Damian Harvey (JIRA) -
Harry Bush (JIRA)
-
Moritz Winter (JIRA)