From issues at jboss.org  Wed Nov 12 04:45:30 2014
From: issues at jboss.org (Anonymous (JIRA))
Date: Wed, 12 Nov 2014 04:45:30 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) <s:link view="..."
 propagation="begin"> + login-required="true" throws
 "java.lang.IllegalStateException: long-running conversation already active"
 after login succeeded
In-Reply-To: <JIRA.12387618.1244289869000@Atlassian.JIRA>
References: <JIRA.12387618.1244289869000@Atlassian.JIRA>
	<JIRA.12387618.1244289869000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12387618.1244289869000.204.1415785530296@Atlassian.JIRA>


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

Anonymous commented on JBSEAM-4226:
-----------------------------------

http://lucidlifestyles.com/nike/nike-blazer-woven_c88http://lucidlifestyles.com/nike/nike-blazer-woven_c88
 <a href="http://lucidlifestyles.com/nike/shox-nz_c190" >cheap Shox NZ</a>
[url=http://lucidlifestyles.com/nike/shox-nz_c190]cheap Shox NZ[/url]

> <s:link view="..." propagation="begin"> + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4226
>                 URL: https://issues.jboss.org/browse/JBSEAM-4226
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.CR2
>         Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot
>            Reporter: Gena
>
> Hello,
> if i use <s:link view="/login/start.xhtml" 	immediate="true" propagation="begin"> and the view pointed by s:link requires login within the pages.xml i get an exception: " java.lang.IllegalStateException: long-running conversation already active" after login succeeded and before redirect should occur. 
> The problem is present since about 6 weeks. If i change the  propagation to "none" it works, but the request from the link above is proceessed within the current long running conversation and if this conversation timed out, i always get the conversation timeout redirect an can not simple leave the current page with one click on the link described above.
> Switch to the previous Seam build resolves the problem.
> Gena



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 12 04:45:30 2014
From: issues at jboss.org (Anonymous (JIRA))
Date: Wed, 12 Nov 2014 04:45:30 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) <s:link view="..."
 propagation="begin"> + login-required="true" throws
 "java.lang.IllegalStateException: long-running conversation already active"
 after login succeeded
In-Reply-To: <JIRA.12387618.1244289869000@Atlassian.JIRA>
References: <JIRA.12387618.1244289869000@Atlassian.JIRA>
	<JIRA.12387618.1244289869000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12387618.1244289869000.207.1415785530476@Atlassian.JIRA>


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

Anonymous commented on JBSEAM-4226:
-----------------------------------

http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32
 <a href="http://lucidlifestyles.com/ugg/infants-ugg-boots_c2" >Infants UGG Boots sale</a>
[url=http://lucidlifestyles.com/ugg/infants-ugg-boots_c2]Infants UGG Boots sale[/url]

> <s:link view="..." propagation="begin"> + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4226
>                 URL: https://issues.jboss.org/browse/JBSEAM-4226
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.CR2
>         Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot
>            Reporter: Gena
>
> Hello,
> if i use <s:link view="/login/start.xhtml" 	immediate="true" propagation="begin"> and the view pointed by s:link requires login within the pages.xml i get an exception: " java.lang.IllegalStateException: long-running conversation already active" after login succeeded and before redirect should occur. 
> The problem is present since about 6 weeks. If i change the  propagation to "none" it works, but the request from the link above is proceessed within the current long running conversation and if this conversation timed out, i always get the conversation timeout redirect an can not simple leave the current page with one click on the link described above.
> Switch to the previous Seam build resolves the problem.
> Gena



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 12 05:40:29 2014
From: issues at jboss.org (Anonymous (JIRA))
Date: Wed, 12 Nov 2014 05:40:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to
 allow redirection with parameters
In-Reply-To: <JIRA.12323818.1143320147000@Atlassian.JIRA>
References: <JIRA.12323818.1143320147000@Atlassian.JIRA>
	<JIRA.12323818.1143320147000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12323818.1143320147000.422.1415788829689@Atlassian.JIRA>


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

Anonymous commented on JBSEAM-180:
----------------------------------

http://www.quangminhtrade.com/ads/mbt ???
?u?u? http://www.hoducoltd.com/flash/index.html

> navigation-rules.xml to allow redirection with parameters
> ---------------------------------------------------------
>
>                 Key: JBSEAM-180
>                 URL: https://issues.jboss.org/browse/JBSEAM-180
>             Project: Seam 2
>          Issue Type: Feature Request
>          Components: JSF Integration
>            Reporter: Gavin King
>            Assignee: Gavin King
>             Fix For: 1.1.1.GA
>
>
> We need to enhance JSF's navigation rules facility to support the following:
> <navigation-case>
>    <from-action>#{searchAction.search}</from-action>
>    <to-view-id>searchResults.jsp</to-view-id>
>    <redirect>
>       <param name="searchPattern">#{searchAction.searchPattern}</param>
>    </redirect>
> </navigation-case>
> What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Wed Nov 12 06:05:29 2014
From: issues at jboss.org (Anonymous (JIRA))
Date: Wed, 12 Nov 2014 06:05:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to
 allow redirection with parameters
In-Reply-To: <JIRA.12323818.1143320147000@Atlassian.JIRA>
References: <JIRA.12323818.1143320147000@Atlassian.JIRA>
	<JIRA.12323818.1143320147000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12323818.1143320147000.500.1415790329686@Atlassian.JIRA>


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

Anonymous commented on JBSEAM-180:
----------------------------------

http://www.quangminhtrade.com/fckeditor/mbtstyle.htmlmbt ??????w?????
buy shoes online http://www.g8shutters.com/CSS/mbtjiage.html

> navigation-rules.xml to allow redirection with parameters
> ---------------------------------------------------------
>
>                 Key: JBSEAM-180
>                 URL: https://issues.jboss.org/browse/JBSEAM-180
>             Project: Seam 2
>          Issue Type: Feature Request
>          Components: JSF Integration
>            Reporter: Gavin King
>            Assignee: Gavin King
>             Fix For: 1.1.1.GA
>
>
> We need to enhance JSF's navigation rules facility to support the following:
> <navigation-case>
>    <from-action>#{searchAction.search}</from-action>
>    <to-view-id>searchResults.jsp</to-view-id>
>    <redirect>
>       <param name="searchPattern">#{searchAction.searchPattern}</param>
>    </redirect>
> </navigation-case>
> What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Wed Nov 12 08:07:29 2014
From: issues at jboss.org (=?UTF-8?Q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29?=)
Date: Wed, 12 Nov 2014 08:07:29 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to
 allow redirection with parameters
In-Reply-To: <JIRA.12323818.1143320147000@Atlassian.JIRA>
References: <JIRA.12323818.1143320147000@Atlassian.JIRA>
	<JIRA.12323818.1143320147000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12323818.1143320147000.1238.1415797649980@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlastimil Eli?? updated JBSEAM-180:
-----------------------------------
    Comment: was deleted

(was: http://www.quangminhtrade.com/fckeditor/mbtstyle.htmlmbt ??????w?????
buy shoes online http://www.g8shutters.com/CSS/mbtjiage.html)


> navigation-rules.xml to allow redirection with parameters
> ---------------------------------------------------------
>
>                 Key: JBSEAM-180
>                 URL: https://issues.jboss.org/browse/JBSEAM-180
>             Project: Seam 2
>          Issue Type: Feature Request
>          Components: JSF Integration
>            Reporter: Gavin King
>            Assignee: Gavin King
>             Fix For: 1.1.1.GA
>
>
> We need to enhance JSF's navigation rules facility to support the following:
> <navigation-case>
>    <from-action>#{searchAction.search}</from-action>
>    <to-view-id>searchResults.jsp</to-view-id>
>    <redirect>
>       <param name="searchPattern">#{searchAction.searchPattern}</param>
>    </redirect>
> </navigation-case>
> What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Wed Nov 12 08:07:30 2014
From: issues at jboss.org (=?UTF-8?Q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29?=)
Date: Wed, 12 Nov 2014 08:07:30 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-180) navigation-rules.xml to
 allow redirection with parameters
In-Reply-To: <JIRA.12323818.1143320147000@Atlassian.JIRA>
References: <JIRA.12323818.1143320147000@Atlassian.JIRA>
	<JIRA.12323818.1143320147000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12323818.1143320147000.1242.1415797650256@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlastimil Eli?? updated JBSEAM-180:
-----------------------------------
    Comment: was deleted

(was: http://www.quangminhtrade.com/ads/mbt ???
?u?u? http://www.hoducoltd.com/flash/index.html)


> navigation-rules.xml to allow redirection with parameters
> ---------------------------------------------------------
>
>                 Key: JBSEAM-180
>                 URL: https://issues.jboss.org/browse/JBSEAM-180
>             Project: Seam 2
>          Issue Type: Feature Request
>          Components: JSF Integration
>            Reporter: Gavin King
>            Assignee: Gavin King
>             Fix For: 1.1.1.GA
>
>
> We need to enhance JSF's navigation rules facility to support the following:
> <navigation-case>
>    <from-action>#{searchAction.search}</from-action>
>    <to-view-id>searchResults.jsp</to-view-id>
>    <redirect>
>       <param name="searchPattern">#{searchAction.searchPattern}</param>
>    </redirect>
> </navigation-case>
> What I propose to do is introduce a navigation-rules.xml file and reproduce the functionality of JSF navigation rules in Seam (yuck!).



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Wed Nov 12 08:07:30 2014
From: issues at jboss.org (=?UTF-8?Q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29?=)
Date: Wed, 12 Nov 2014 08:07:30 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) <s:link view="..."
 propagation="begin"> + login-required="true" throws
 "java.lang.IllegalStateException: long-running conversation already active"
 after login succeeded
In-Reply-To: <JIRA.12387618.1244289869000@Atlassian.JIRA>
References: <JIRA.12387618.1244289869000@Atlassian.JIRA>
	<JIRA.12387618.1244289869000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12387618.1244289869000.1245.1415797650435@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlastimil Eli?? updated JBSEAM-4226:
------------------------------------
    Comment: was deleted

(was: http://lucidlifestyles.com/nike/nike-blazer-woven_c88http://lucidlifestyles.com/nike/nike-blazer-woven_c88
 <a href="http://lucidlifestyles.com/nike/shox-nz_c190" >cheap Shox NZ</a>
[url=http://lucidlifestyles.com/nike/shox-nz_c190]cheap Shox NZ[/url])


> <s:link view="..." propagation="begin"> + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4226
>                 URL: https://issues.jboss.org/browse/JBSEAM-4226
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.CR2
>         Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot
>            Reporter: Gena
>
> Hello,
> if i use <s:link view="/login/start.xhtml" 	immediate="true" propagation="begin"> and the view pointed by s:link requires login within the pages.xml i get an exception: " java.lang.IllegalStateException: long-running conversation already active" after login succeeded and before redirect should occur. 
> The problem is present since about 6 weeks. If i change the  propagation to "none" it works, but the request from the link above is proceessed within the current long running conversation and if this conversation timed out, i always get the conversation timeout redirect an can not simple leave the current page with one click on the link described above.
> Switch to the previous Seam build resolves the problem.
> Gena



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Wed Nov 12 08:07:30 2014
From: issues at jboss.org (=?UTF-8?Q?Vlastimil_Eli=C3=A1=C5=A1_=28JIRA=29?=)
Date: Wed, 12 Nov 2014 08:07:30 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4226) <s:link view="..."
 propagation="begin"> + login-required="true" throws
 "java.lang.IllegalStateException: long-running conversation already active"
 after login succeeded
In-Reply-To: <JIRA.12387618.1244289869000@Atlassian.JIRA>
References: <JIRA.12387618.1244289869000@Atlassian.JIRA>
	<JIRA.12387618.1244289869000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12387618.1244289869000.1248.1415797650604@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlastimil Eli?? updated JBSEAM-4226:
------------------------------------
    Comment: was deleted

(was: http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32http://joshadamsrealtor.com/nike/nike-men-air-max-bw_c32
 <a href="http://lucidlifestyles.com/ugg/infants-ugg-boots_c2" >Infants UGG Boots sale</a>
[url=http://lucidlifestyles.com/ugg/infants-ugg-boots_c2]Infants UGG Boots sale[/url])


> <s:link view="..." propagation="begin"> + login-required="true" throws "java.lang.IllegalStateException: long-running conversation already active" after login succeeded
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4226
>                 URL: https://issues.jboss.org/browse/JBSEAM-4226
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.2.CR2
>         Environment: JBoss 4.2.3 Seam 2.1.2CR2 snapshot
>            Reporter: Gena
>
> Hello,
> if i use <s:link view="/login/start.xhtml" 	immediate="true" propagation="begin"> and the view pointed by s:link requires login within the pages.xml i get an exception: " java.lang.IllegalStateException: long-running conversation already active" after login succeeded and before redirect should occur. 
> The problem is present since about 6 weeks. If i change the  propagation to "none" it works, but the request from the link above is proceessed within the current long running conversation and if this conversation timed out, i always get the conversation timeout redirect an can not simple leave the current page with one click on the link described above.
> Switch to the previous Seam build resolves the problem.
> Gena



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)


From issues at jboss.org  Mon Nov 17 14:03:39 2014
From: issues at jboss.org (Daniel Coughlin (JIRA))
Date: Mon, 17 Nov 2014 14:03:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org
	- Seam
In-Reply-To: <JIRA.12557570.1416250974000@Atlassian.JIRA>
References: <JIRA.12557570.1416250974000@Atlassian.JIRA>
	<JIRA.12557570.1416250974939@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557570.1416250974000.1415.1416251019322@Atlassian.JIRA>

Daniel Coughlin created JBSEAM-5141:
---------------------------------------

             Summary: Broken Links on JBoss.org - Seam
                 Key: JBSEAM-5141
                 URL: https://issues.jboss.org/browse/JBSEAM-5141
             Project: Seam 2
          Issue Type: Bug
            Reporter: Daniel Coughlin


The following broken link is currently listed against this project on www.jboss.org/projects.

http://www.seamframework.org/Seam2/Documentation - Documentation
http://www.seamframework.org/Documentation/KnowledgeBase - Community
http://www.seamframework.org/Community/SeamUsers - User Forum
http://www.seamframework.org/Download - Download (Forbidden)

If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page.




--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Tue Nov 18 04:22:39 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 18 Nov 2014 04:22:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org
	- Seam
In-Reply-To: <JIRA.12557570.1416250974000@Atlassian.JIRA>
References: <JIRA.12557570.1416250974000@Atlassian.JIRA>
	<JIRA.12557570.1416250974000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557570.1416250974000.2228.1416302559471@Atlassian.JIRA>


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

Marek Novotny commented on JBSEAM-5141:
---------------------------------------

The links was changed after seamframework.org was restored from backup to new static web (that web doesn't use Magnolia AFAIK), so new links are:
http://www.seamframework.org/Seam2/Documentation.html - Documentation
http://www.seamframework.org/Documentation/KnowledgeBase.html - Community
https://developer.jboss.org/en/seam - User Forum
http://www.seamframework.org/Downloads.html - Download

> Broken Links on JBoss.org - Seam
> --------------------------------
>
>                 Key: JBSEAM-5141
>                 URL: https://issues.jboss.org/browse/JBSEAM-5141
>             Project: Seam 2
>          Issue Type: Bug
>            Reporter: Daniel Coughlin
>
> The following broken link is currently listed against this project on www.jboss.org/projects.
> http://www.seamframework.org/Seam2/Documentation - Documentation
> http://www.seamframework.org/Documentation/KnowledgeBase - Community
> http://www.seamframework.org/Community/SeamUsers - User Forum
> http://www.seamframework.org/Download - Download (Forbidden)
> If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Tue Nov 18 04:23:39 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 18 Nov 2014 04:23:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org
	- Seam
In-Reply-To: <JIRA.12557570.1416250974000@Atlassian.JIRA>
References: <JIRA.12557570.1416250974000@Atlassian.JIRA>
	<JIRA.12557570.1416250974000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557570.1416250974000.2231.1416302619644@Atlassian.JIRA>


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

Marek Novotny edited comment on JBSEAM-5141 at 11/18/14 4:23 AM:
-----------------------------------------------------------------

The links was changed after seamframework.org was restored from backup to new static web (that web doesn't use Magnolia AFAIK), so new links are:
http://www.seamframework.org/Seam2/Documentation.html - Documentation
http://www.seamframework.org/Documentation/KnowledgeBase.html - Community
https://developer.jboss.org/en/seam - User Forum
http://www.seamframework.org/Seam2/Downloads.html - Download


was (Author: manarh):
The links was changed after seamframework.org was restored from backup to new static web (that web doesn't use Magnolia AFAIK), so new links are:
http://www.seamframework.org/Seam2/Documentation.html - Documentation
http://www.seamframework.org/Documentation/KnowledgeBase.html - Community
https://developer.jboss.org/en/seam - User Forum
http://www.seamframework.org/Downloads.html - Download

> Broken Links on JBoss.org - Seam
> --------------------------------
>
>                 Key: JBSEAM-5141
>                 URL: https://issues.jboss.org/browse/JBSEAM-5141
>             Project: Seam 2
>          Issue Type: Bug
>            Reporter: Daniel Coughlin
>
> The following broken link is currently listed against this project on www.jboss.org/projects.
> http://www.seamframework.org/Seam2/Documentation - Documentation
> http://www.seamframework.org/Documentation/KnowledgeBase - Community
> http://www.seamframework.org/Community/SeamUsers - User Forum
> http://www.seamframework.org/Download - Download (Forbidden)
> If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Tue Nov 18 04:23:39 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 18 Nov 2014 04:23:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5141) Broken Links on JBoss.org
	- Seam
In-Reply-To: <JIRA.12557570.1416250974000@Atlassian.JIRA>
References: <JIRA.12557570.1416250974000@Atlassian.JIRA>
	<JIRA.12557570.1416250974000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557570.1416250974000.2234.1416302619851@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-5141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reassigned JBSEAM-5141:
-------------------------------------

    Assignee: Marek Novotny


> Broken Links on JBoss.org - Seam
> --------------------------------
>
>                 Key: JBSEAM-5141
>                 URL: https://issues.jboss.org/browse/JBSEAM-5141
>             Project: Seam 2
>          Issue Type: Bug
>            Reporter: Daniel Coughlin
>            Assignee: Marek Novotny
>
> The following broken link is currently listed against this project on www.jboss.org/projects.
> http://www.seamframework.org/Seam2/Documentation - Documentation
> http://www.seamframework.org/Documentation/KnowledgeBase - Community
> http://www.seamframework.org/Community/SeamUsers - User Forum
> http://www.seamframework.org/Download - Download (Forbidden)
> If you maintain a project.properties file that you have told the jboss.org team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 19 05:19:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 19 Nov 2014 05:19:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter
	ignored
In-Reply-To: <JIRA.12557668.1416392323000@Atlassian.JIRA>
References: <JIRA.12557668.1416392323000@Atlassian.JIRA>
	<JIRA.12557668.1416392323997@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557668.1416392323000.5115.1416392379354@Atlassian.JIRA>

Robert Becker created JBSEAM-5142:
-------------------------------------

             Summary: s:link fragment parameter ignored
                 Key: JBSEAM-5142
                 URL: https://issues.jboss.org/browse/JBSEAM-5142
             Project: Seam 2
          Issue Type: Bug
          Components: JSF Controls
    Affects Versions: 2.3.1.Final
            Reporter: Robert Becker


Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute is ignored. 

Code example:
{code:xml}
<s:link value="#{msg.back}" propagation="none" fragment="article_#{param['samsArticleComponent.showSingleArticle']}">
                    <f:param name="samsArticleComponent.page" value="#{param['samsArticleComponent.page']}"/>
                </s:link>
{code}

Produces the following href attribute: https://[...]/cms/home.xhtml?samsArticleComponent.page=0

I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2:
{code:title=Seam 2.2.2}
    @Override
    public String getEncodedUrl() {
        return FacesContext.getCurrentInstance().getExternalContext().encodeActionURL(super.getEncodedUrl());
    }
{code}

{code:title=Seam 2.3.1}
    @Override
    public String getEncodedUrl() 
    {
       FacesContext facesContext = FacesContext.getCurrentInstance();
       return facesContext.getApplication().getViewHandler().getBookmarkableURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false);
    }
{code}

In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I guess this got lost when switching to the new method.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 19 05:19:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 19 Nov 2014 05:19:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter
	ignored
In-Reply-To: <JIRA.12557668.1416392323000@Atlassian.JIRA>
References: <JIRA.12557668.1416392323000@Atlassian.JIRA>
	<JIRA.12557668.1416392323000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557668.1416392323000.5117.1416392379396@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Becker updated JBSEAM-5142:
----------------------------------
    Description: 
Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute is ignored. 

Code example:
{code:xml}
<s:link value="#{msg.back}" propagation="none" fragment="article_#{param['samsArticleComponent.showSingleArticle']}">
  <f:param name="samsArticleComponent.page" value="#{param['samsArticleComponent.page']}"/>
</s:link>
{code}

Produces the following href attribute: https://[...]/cms/home.xhtml?samsArticleComponent.page=0

I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2:
{code:title=Seam 2.2.2}
    @Override
    public String getEncodedUrl() {
        return FacesContext.getCurrentInstance().getExternalContext().encodeActionURL(super.getEncodedUrl());
    }
{code}

{code:title=Seam 2.3.1}
    @Override
    public String getEncodedUrl() 
    {
       FacesContext facesContext = FacesContext.getCurrentInstance();
       return facesContext.getApplication().getViewHandler().getBookmarkableURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false);
    }
{code}

In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I guess this got lost when switching to the new method.

  was:
Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute is ignored. 

Code example:
{code:xml}
<s:link value="#{msg.back}" propagation="none" fragment="article_#{param['samsArticleComponent.showSingleArticle']}">
                    <f:param name="samsArticleComponent.page" value="#{param['samsArticleComponent.page']}"/>
                </s:link>
{code}

Produces the following href attribute: https://[...]/cms/home.xhtml?samsArticleComponent.page=0

I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2:
{code:title=Seam 2.2.2}
    @Override
    public String getEncodedUrl() {
        return FacesContext.getCurrentInstance().getExternalContext().encodeActionURL(super.getEncodedUrl());
    }
{code}

{code:title=Seam 2.3.1}
    @Override
    public String getEncodedUrl() 
    {
       FacesContext facesContext = FacesContext.getCurrentInstance();
       return facesContext.getApplication().getViewHandler().getBookmarkableURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false);
    }
{code}

In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I guess this got lost when switching to the new method.



> s:link fragment parameter ignored
> ---------------------------------
>
>                 Key: JBSEAM-5142
>                 URL: https://issues.jboss.org/browse/JBSEAM-5142
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Controls
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute is ignored. 
> Code example:
> {code:xml}
> <s:link value="#{msg.back}" propagation="none" fragment="article_#{param['samsArticleComponent.showSingleArticle']}">
>   <f:param name="samsArticleComponent.page" value="#{param['samsArticleComponent.page']}"/>
> </s:link>
> {code}
> Produces the following href attribute: https://[...]/cms/home.xhtml?samsArticleComponent.page=0
> I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2:
> {code:title=Seam 2.2.2}
>     @Override
>     public String getEncodedUrl() {
>         return FacesContext.getCurrentInstance().getExternalContext().encodeActionURL(super.getEncodedUrl());
>     }
> {code}
> {code:title=Seam 2.3.1}
>     @Override
>     public String getEncodedUrl() 
>     {
>        FacesContext facesContext = FacesContext.getCurrentInstance();
>        return facesContext.getApplication().getViewHandler().getBookmarkableURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false);
>     }
> {code}
> In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I guess this got lost when switching to the new method.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 19 05:31:40 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 19 Nov 2014 05:31:40 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5142) s:link fragment parameter
	ignored
In-Reply-To: <JIRA.12557668.1416392323000@Atlassian.JIRA>
References: <JIRA.12557668.1416392323000@Atlassian.JIRA>
	<JIRA.12557668.1416392323000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12557668.1416392323000.5196.1416393100046@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5142:
---------------------------------------

I just switched to the new h:link tag which also supports the fragment attribute and works as expected.

> s:link fragment parameter ignored
> ---------------------------------
>
>                 Key: JBSEAM-5142
>                 URL: https://issues.jboss.org/browse/JBSEAM-5142
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Controls
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3.x (from 2.2.2), the s:link fragment attribute is ignored. 
> Code example:
> {code:xml}
> <s:link value="#{msg.back}" propagation="none" fragment="article_#{param['samsArticleComponent.showSingleArticle']}">
>   <f:param name="samsArticleComponent.page" value="#{param['samsArticleComponent.page']}"/>
> </s:link>
> {code}
> Produces the following href attribute: https://[...]/cms/home.xhtml?samsArticleComponent.page=0
> I noticed changes in org.jboss.seam.ui.util.ViewUrlBuilder.java since 2.2.2:
> {code:title=Seam 2.2.2}
>     @Override
>     public String getEncodedUrl() {
>         return FacesContext.getCurrentInstance().getExternalContext().encodeActionURL(super.getEncodedUrl());
>     }
> {code}
> {code:title=Seam 2.3.1}
>     @Override
>     public String getEncodedUrl() 
>     {
>        FacesContext facesContext = FacesContext.getCurrentInstance();
>        return facesContext.getApplication().getViewHandler().getBookmarkableURL(facesContext, this.viewId, getParametersAsMap(getParameters()), false);
>     }
> {code}
> In Seam 2.2.2, super.getEncodedUrl() took care of including the fragment. I guess this got lost when switching to the new method.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 26 04:31:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 26 Nov 2014 04:31:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274942@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.18980.1416994299756@Atlassian.JIRA>

Robert Becker created JBSEAM-5143:
-------------------------------------

             Summary: Random IllegalArgumentException: Stack must not be null
                 Key: JBSEAM-5143
                 URL: https://issues.jboss.org/browse/JBSEAM-5143
             Project: Seam 2
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.3.1.Final
            Reporter: Robert Becker






--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 26 04:38:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 26 Nov 2014 04:38:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.18999.1416994719367@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Becker updated JBSEAM-5143:
----------------------------------
    Description: 
Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". Perhaps this is related to No long-running conversations - IllegalArgumentException: Stack must not be null, but I really don't know what I am doing wrong. The application worked fine for several years until now.

The full stack trace is listed here: http://pastebin.com/RjLndvnE

The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.

I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.

I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.

Besides Seam 2.3, the following libraries are used:
- Mojarra 2.1.29
- RF 4.5 (exception also occurred with 4.3.x)
- Omnifaces 1.10RC1 (will upgrade to 2.0)
- Primefaces 5.1




> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". Perhaps this is related to No long-running conversations - IllegalArgumentException: Stack must not be null, but I really don't know what I am doing wrong. The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 26 04:38:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 26 Nov 2014 04:38:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.19001.1416994719414@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Becker updated JBSEAM-5143:
----------------------------------
    Description: 
Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.

The full stack trace is listed here: http://pastebin.com/RjLndvnE

The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.

I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.

I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.

Besides Seam 2.3, the following libraries are used:
- Mojarra 2.1.29
- RF 4.5 (exception also occurred with 4.3.x)
- Omnifaces 1.10RC1 (will upgrade to 2.0)
- Primefaces 5.1



  was:
Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". Perhaps this is related to No long-running conversations - IllegalArgumentException: Stack must not be null, but I really don't know what I am doing wrong. The application worked fine for several years until now.

The full stack trace is listed here: http://pastebin.com/RjLndvnE

The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.

I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.

I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.

Besides Seam 2.3, the following libraries are used:
- Mojarra 2.1.29
- RF 4.5 (exception also occurred with 4.3.x)
- Omnifaces 1.10RC1 (will upgrade to 2.0)
- Primefaces 5.1





> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 26 04:42:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 26 Nov 2014 04:42:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.19017.1416994959366@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/JBSEAM-5143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Becker updated JBSEAM-5143:
----------------------------------
    Description: 
Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.

The full stack trace is listed here: http://pastebin.com/RjLndvnE

The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.

I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.

I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.

Besides Seam 2.3, the following libraries are used:
- Mojarra 2.1.29
- RF 4.5 (exception also occurred with 4.3.x)
- Omnifaces 1.10RC1 (will upgrade to 2.0)
- Primefaces 5.1



  was:
Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.

The full stack trace is listed here: http://pastebin.com/RjLndvnE

The exception randomly happens (in about 1 of 100 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.

I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.

I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.

Besides Seam 2.3, the following libraries are used:
- Mojarra 2.1.29
- RF 4.5 (exception also occurred with 4.3.x)
- Omnifaces 1.10RC1 (will upgrade to 2.0)
- Primefaces 5.1





> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Wed Nov 26 12:25:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Wed, 26 Nov 2014 12:25:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.20705.1417022739339@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

After adding some more detailed information to the exception reports (esp. request parameters) I have noticed that in at least one case the conversation id parameter was definitely present in the list of request parameters. Even though, the conversation stack was null. Could it be that the conversation is accessed before the seam manager is properly initialized?

Here is the stack trace belonging to said exception: http://pastebin.com/3kw1W49Z

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Fri Nov 28 05:12:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Fri, 28 Nov 2014 05:12:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.24332.1417169559753@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

I set the seam log level to debug and perhaps found a clue. This is a request on a page which lead to said exception:

Information: 2014-11-28 10:54:46,270 DEBUG - >>> Begin JSF request for /SAMS/ma/index.xhtml
Information: 2014-11-28 10:41:31,149 DEBUG - beginning transaction prior to phase: RESTORE_VIEW 1
Information: 2014-11-28 10:41:31,149 DEBUG - beginning JTA transaction
Information: 2014-11-28 10:41:31,150 DEBUG - committing transaction after phase: RESTORE_VIEW 1
Information: 2014-11-28 10:41:31,150 DEBUG - committing JTA transaction
Information: 2014-11-28 10:41:31,150 DEBUG - beginning transaction prior to phase: RENDER_RESPONSE 6
Information: 2014-11-28 10:41:31,150 DEBUG - beginning JTA transaction
Information: 2014-11-28 10:41:31,150 DEBUG - trying to inject with hierarchical context search: samsDatabase
Information: 2014-11-28 10:41:31,151 DEBUG - created seam managed persistence context from EntityManagerFactory
Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarchical context search: identity
Information: 2014-11-28 10:41:31,151 DEBUG - trying to inject with hierarchical context search: identity
Information: Hibernate: /* SELECT [...]
Information: 2014-11-28 10:41:31,154 DEBUG - Beginning long-running conversation
Information: 2014-11-28 10:41:31,158 DEBUG - reading exception mappings from /WEB-INF/pages.xml
Information: 2014-11-28 10:41:31,161 ERROR - swallowing exception
javax.el.ELException: java.lang.IllegalArgumentException: Stack must not be null

And this is a request for the same page which was processed without error:

Information: 2014-11-28 10:54:46,271 DEBUG - beginning transaction prior to phase: RESTORE_VIEW 1
Information: 2014-11-28 10:54:46,271 DEBUG - beginning JTA transaction
Information: 2014-11-28 10:54:46,273 DEBUG - isPageContextActive is null
Information: 2014-11-28 10:54:46,273 DEBUG - Page Context will be lazilly created
Information: 2014-11-28 10:54:46,274 DEBUG - No stored conversation
Information: 2014-11-28 10:54:46,274 DEBUG - committing transaction after phase: RESTORE_VIEW 1
Information: 2014-11-28 10:54:46,274 DEBUG - committing JTA transaction
Information: 2014-11-28 10:54:46,275 DEBUG - beginning transaction prior to phase: RENDER_RESPONSE 6
Information: 2014-11-28 10:54:46,275 DEBUG - beginning JTA transaction
Information: 2014-11-28 10:54:46,369 DEBUG - trying to inject with hierarchical context search: samsDatabase
Information: 2014-11-28 10:54:46,371 DEBUG - created seam managed persistence context from EntityManagerFactory
Information: 2014-11-28 10:54:46,371 DEBUG - trying to inject with hierarchical context search: identity
Information: Hibernate: /* SELECT [...]
Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarchical context search: samsDatabase
Information: 2014-11-28 10:54:46,546 DEBUG - trying to inject with hierarchical context search: identity
... and so on and later: "Beginning long-running conversation" (as expected)

The main difference in the latter request is that "isPageContextActive is null" is printed out by Contexts.isPageContextActive(). The method is commented with "Is PageContext set? If not, it is lazily created in case of RESTORE_VIEW is processing. This is a requirement for starting CONVERSATION - JSF2 change". Could it be that one condition here is not applied correctly?

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Fri Nov 28 05:19:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Fri, 28 Nov 2014 05:19:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.24344.1417169979345@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

I am currently running the latest 2.3. nightly build which did not bring any improvement for this issue.

I also removed Omnifaces completely to reduce the pool of possible causes which also changed nothing.

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Fri Nov 28 07:55:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Fri, 28 Nov 2014 07:55:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.24637.1417179339353@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

I noticed something else being quirky: I have an issue with a certain bean which worked fine with Seam 2.2.x and has a prepare method annotated with:

@Create
@Begin(nested = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }

The bean is initialized simply by being referenced in the view (which is linked via s:link from the main conversation view). The problem here is that the new conversation id it not propagated properly when submitting a form within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. Perhaps this is related to the main issue above.

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Fri Nov 28 08:06:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Fri, 28 Nov 2014 08:06:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.24648.1417179999348@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

Disabling partial state saving does not prevent the IllegalArgumentException to occur.

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Fri Nov 28 08:19:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Fri, 28 Nov 2014 08:19:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.24654.1417180779732@Atlassian.JIRA>


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

Robert Becker edited comment on JBSEAM-5143 at 11/28/14 8:19 AM:
-----------------------------------------------------------------

I noticed something else being quirky: I have an issue with a certain bean which worked fine with Seam 2.2.x and has a prepare method annotated with:

@Create
@Begin(nested = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }

The bean is initialized simply by being referenced in the view (which is linked via s:link from the main conversation view). The problem here is that the new conversation id it not propagated properly when submitting a form within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. Perhaps this is related to the main issue above.

The generated html form has an action parameter containing the original (parent) id which got (correctly) appended to the url when redirect to the new view. Normally it should have been removed from the form action and the correct one should be added as hidden input field. 


was (Author: r0b3n):
I noticed something else being quirky: I have an issue with a certain bean which worked fine with Seam 2.2.x and has a prepare method annotated with:

@Create
@Begin(nested = true, flushMode = FlushModeType.MANUAL)
public void prepare() { ... }

The bean is initialized simply by being referenced in the view (which is linked via s:link from the main conversation view). The problem here is that the new conversation id it not propagated properly when submitting a form within the view using an h:commandButton. Instead, the parent conversation id is propagated and the bean with its child conversation is recreated in the next request. I tested the same action with an s:button, which works, though. Perhaps this is related to the main issue above.

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)

From issues at jboss.org  Sun Nov 30 07:01:39 2014
From: issues at jboss.org (Robert Becker (JIRA))
Date: Sun, 30 Nov 2014 07:01:39 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5143) Random
 IllegalArgumentException: Stack must not be null
In-Reply-To: <JIRA.12558207.1416994274000@Atlassian.JIRA>
References: <JIRA.12558207.1416994274000@Atlassian.JIRA>
	<JIRA.12558207.1416994274000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12558207.1416994274000.25129.1417348899496@Atlassian.JIRA>


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

Robert Becker commented on JBSEAM-5143:
---------------------------------------

The whole problem seems strongly related to https://issues.jboss.org/browse/JBSEAM-4898. Could it be that changes to Mojarra 2.1.x caused some regression?

> Random IllegalArgumentException: Stack must not be null
> -------------------------------------------------------
>
>                 Key: JBSEAM-5143
>                 URL: https://issues.jboss.org/browse/JBSEAM-5143
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.1.Final
>            Reporter: Robert Becker
>
> Since upgrading to Seam 2.3 with Mojarra 2.1.29 on glassfish v3 from Seam 2.2.2, I get random IllegalArgumentExceptions with the message "Stack must not be null". The application worked fine for several years until now.
> The full stack trace is listed here: http://pastebin.com/RjLndvnE
> The exception randomly happens (in about 1 of 500 requests) when navigating between pages, submitting forms, switching (RichFaces) tabs and so on.
> I believe restarting glassfish and/or enabling client side state saving reduces the frequency of the issue whereas it seems to happen more often after multiple successive redeployments during development.  Sadly, due to several dependencies this is already in production but happens far less often there, but it still happens daily according to the server logs.
> I have also posted this on stackoverflow (http://stackoverflow.com/questions/27107870/seam-2-3-illegalargumentexception-stack-must-not-be-null) but have not received any answers yet.
> Besides Seam 2.3, the following libraries are used:
> - Mojarra 2.1.29
> - RF 4.5 (exception also occurred with 4.3.x)
> - Omnifaces 1.10RC1 (will upgrade to 2.0)
> - Primefaces 5.1



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)