April 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5083) SeamViewHandler adds conversation id even if conversation is not long running

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5083?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5083: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> made a comment on [bug 921660|https://bugzilla.redhat.com/show_bug.cgi?id=921660] Edited release note and inserted it into the 2.2.0 RN book. Docs stage URL: https://documentation-devel.engineering.redhat.com/docs/en-US/JBoss_Web_F... Build: JBoss_Web_Framework_Kit-2.2.0_Release_Notes-2.2-en-US-0-23 > SeamViewHandler adds conversation id even if conversation is not long running > ----------------------------------------------------------------------------- > > Key: JBSEAM-5083 > URL: https://issues.jboss.org/browse/JBSEAM-5083 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Seam adds a conversation id even if the conversation is not long running into URL. > Note that the way how seam propagates conversation id has changed since Seam 2.2, so that now it uses the cid= in places where Seam2.2 would use the page context, so in some cases the "cid" parameter would be correctly present in a Seam2.3 application even if it was not present in the same Seam 2.2 application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5001) Deadlock between SFSB EJB lock and Component.getInstanceFromFactory factoryLock calling factory from the same component

by Marek Schmidt (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5001?page=com.atlassian.jira.plugi... ] Marek Schmidt commented on JBSEAM-5001: --------------------------------------- Yes, but when you look at the server log, you'll see that the error is a timeout at the SFSB lock, which resolves the deadlock after 5 seconds. Caused by: javax.ejb.ConcurrentAccessTimeoutException: JBAS014360: EJB 3.1 FR 4.3.14.1 concurrent access timeout on org.jboss.invocation.InterceptorContext@40fa6677 - could not obtain lock within 5000 MILLISECONDS at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:117) [jboss-as-ejb3-7.2.0.Final-redhat-4.jar:7.2.0.Final-r edhat-4] > Deadlock between SFSB EJB lock and Component.getInstanceFromFactory factoryLock calling factory from the same component > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBSEAM-5001 > URL: https://issues.jboss.org/browse/JBSEAM-5001 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.0.BETA2 > Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT r14986 > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > Attachments: JBSEAM-5001.ear, JBSEAM-5001.tar.gz, test.py > > > The following sample demonstrates a deadlock between SFSB lock and the Component.getInstanceFromFactory factoryLock: > {code} > @Stateful > @Scope(ScopeType.SESSION) > @Name("test") > public class TestAction implements Test > { > > public String test() { > Thread.sleep(500); > Component.getInstance("testString", true); > return "test"; > } > > @Factory(value="testString", scope=ScopeType.SESSION) > public String getTestString() { > return "testString"; > } > @Remove > public void remove() {} > } > {code} > when test.xhtml contains: > {code} > <h:outputText value="#{test.test()} " /> > {code} > and othertest.xhtml contains: > {code} > <h:outputText value="#{testString} " /> > {code} > If the othertest.seam is requested just after (<500ms after) the test.seam with the same session cookie. > The problem seems to be that the #{test.test()} first locks the TestAction SFSB lock and then the Seam factory lock in the Component.getInstance call, while #{testString} locks the factoryLock first. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SEAMFACES-214) @ViewConfig after authorization redirect back to original page throws exception

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] Bernard Labno commented on SEAMFACES-214: ----------------------------------------- Why don't we observe org.jboss.seam.security.events.LoggedInEvent instead of PreNavigateEvent? Here's my workaround: {code:lang=java} @Specializes public class QwestmarkLoginListener extends LoginListener { public void redirectAfterLoginIfNeeded(@Observes LoggedInEvent event) { final FacesContext facesContext = FacesContext.getCurrentInstance(); Map<String, Object> sessionMap = facesContext.getExternalContext().getSessionMap(); super.observePostLoginEvent(new PostLoginEvent(facesContext, sessionMap)); } @Override public void observePostLoginEvent(@Observes PostLoginEvent event) { // We need to block bahavior of superclass } } {code} > @ViewConfig after authorization redirect back to original page throws exception > ------------------------------------------------------------------------------- > > Key: SEAMFACES-214 > URL: https://issues.jboss.org/browse/SEAMFACES-214 > Project: Seam Faces > Issue Type: Bug > Affects Versions: 3.1.0.Beta3 > Environment: Jboss 7.0.2 > Reporter: christoph langer > > See > http://seamframework.org/Community/ViewScopeRedirectAfterLoginErrorIllega... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5002) Components included with ui:include src="#{pageScopedViewId} broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5002?page=com.atlassian.jira.plugi... ] Marek Novotny updated JBSEAM-5002: ---------------------------------- Fix Version/s: The future (was: 2.3.1.CR1) > Components included with ui:include src="#{pageScopedViewId} broken > ------------------------------------------------------------------- > > Key: JBSEAM-5002 > URL: https://issues.jboss.org/browse/JBSEAM-5002 > Project: Seam 2 > Issue Type: Bug > Components: JSF Integration > Affects Versions: 2.3.0.BETA2, 2.3.0.Final > Environment: JBoss AS 7.1.2, Seam 2.3.0.CR1-SNAPSHOT (r14986) > Reporter: Marek Schmidt > Assignee: Marek Novotny > Fix For: The future > > Attachments: JBSEAM-5002.ear, JBSEAM-5002.tar.gz > > > The following scenario that used to work in AS5/Seam2.2 doesn't work anymore in AS7/Seam2.3 for page-scoped and conversation-scoped "viewId" components: > index.xhtml: > {code} > <h:form> > <h:commandButton action="#{viewId.component1}" value="Component 1" /> > <h:commandButton action="#{viewId.component2}" value="Component 2" /> > </h:form> > > <ui:include src="#{viewId.viewId}"/> > {code} > {code} > @Scope(ScopeType.PAGE) > @Name("viewId") > public class ViewIdComponent implements Serializable > { > private String viewId = "/component1.xhtml"; > > public void setViewId(String viewId) { > this.viewId = viewId; > } > > public String getViewId() { > return viewId; > } > > public void component1() { > setViewId("/component1.xhtml"); > } > > public void component2() { > setViewId("/component2.xhtml"); > } > } > {code} > (compoent1 and 2 are redacted, contain a simple form) > Only the first component works properly, actions in "component2" doesn't seem to be called after switching to "Component 2". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5064) s:link conversation propagation none broken

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5064?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5064. ----------------------------------- Resolution: Done fixed already by JBSEAM-5083 > s:link conversation propagation none broken > ------------------------------------------- > > Key: JBSEAM-5064 > URL: https://issues.jboss.org/browse/JBSEAM-5064 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.0.0, Seam 2.3.1-SNAPSHOT > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > s:link / s:button with propagation="none" does propagate conversations even when it shouldn't since the fix for JBSEAM-4976, as the conversation id gets appended always by the SeamViewHandler. > Also note that with propagation="join", the conversation id is appended two times there (once from the s:link and once by the SeamViewHandler) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5089) Update jboss-as-maven plugin to use newer compatible version with latest AS 7/8 releases

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5089?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5089. --------------------------------- Assignee: Marek Novotny Resolution: Done > Update jboss-as-maven plugin to use newer compatible version with latest AS 7/8 releases > ---------------------------------------------------------------------------------------- > > Key: JBSEAM-5089 > URL: https://issues.jboss.org/browse/JBSEAM-5089 > Project: Seam 2 > Issue Type: Enhancement > Components: Examples > Affects Versions: 2.3.0.Final > Reporter: Marek Novotny > Assignee: Marek Novotny > Fix For: 2.3.1.CR1 > > > Update version of 7.1.1.Final to 7.3.Final to be able to deploy examples also on newer JBoss AS 7/8 versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5089) Update jboss-as-maven plugin to use newer compatible version with latest AS 7/8 releases

by Marek Novotny (JIRA)

Marek Novotny created JBSEAM-5089: ------------------------------------- Summary: Update jboss-as-maven plugin to use newer compatible version with latest AS 7/8 releases Key: JBSEAM-5089 URL: https://issues.jboss.org/browse/JBSEAM-5089 Project: Seam 2 Issue Type: Enhancement Components: Examples Affects Versions: 2.3.0.Final Reporter: Marek Novotny Fix For: 2.3.1.CR1 Update version of 7.1.1.Final to 7.3.Final to be able to deploy examples also on newer JBoss AS 7/8 versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (SEAMFACES-214) @ViewConfig after authorization redirect back to original page throws exception

by Bernard Labno (JIRA)

[ https://issues.jboss.org/browse/SEAMFACES-214?page=com.atlassian.jira.plu... ] Bernard Labno commented on SEAMFACES-214: ----------------------------------------- Wulf, this does not solve much. PostLoginEvent is raised after JSF navigation rule is selected, but after executed, so the response is not yet comitted. > @ViewConfig after authorization redirect back to original page throws exception > ------------------------------------------------------------------------------- > > Key: SEAMFACES-214 > URL: https://issues.jboss.org/browse/SEAMFACES-214 > Project: Seam Faces > Issue Type: Bug > Affects Versions: 3.1.0.Beta3 > Environment: Jboss 7.0.2 > Reporter: christoph langer > > See > http://seamframework.org/Community/ViewScopeRedirectAfterLoginErrorIllega... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5081) Upgrade Hibernate Search version to latest final 4.2.0.Final

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5081?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-5081. --------------------------------- > Upgrade Hibernate Search version to latest final 4.2.0.Final > ------------------------------------------------------------ > > Key: JBSEAM-5081 > URL: https://issues.jboss.org/browse/JBSEAM-5081 > Project: Seam 2 > Issue Type: Bug > Components: Build > Reporter: Marek Novotny > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > Update latest versions through org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final BOM -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5081) Upgrade Hibernate Search version to latest final 4.2.0.Final

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5081?page=com.atlassian.jira.plugi... ] Marek Novotny resolved JBSEAM-5081. ----------------------------------- Resolution: Done > Upgrade Hibernate Search version to latest final 4.2.0.Final > ------------------------------------------------------------ > > Key: JBSEAM-5081 > URL: https://issues.jboss.org/browse/JBSEAM-5081 > Project: Seam 2 > Issue Type: Bug > Components: Build > Reporter: Marek Novotny > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.1.CR1 > > > Update latest versions through org.jboss.bom:jboss-javaee-6.0-with-hibernate:1.0.4.Final BOM -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2013