September 2012 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2286) MDB activated too early to use Seam components as a standard EJB

by Siarhei Dudzin (JIRA)

MDB activated too early to use Seam components as a standard EJB ---------------------------------------------------------------- Key: JBSEAM-2286 URL: http://jira.jboss.com/jira/browse/JBSEAM-2286 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA Reporter: Siarhei Dudzin Priority: Critical As specified in the forum reference I have an MDB which uses a SLSB (also declared as Seam component) with business logic. If I deploy the application and there are already messages in the queue I get the following exception: javax.ejb.EJBTransactionRolledbackException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside the an initialized application at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:87) at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130) at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:195) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:62) at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:249) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:268) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:138) at $Proxy111.onMessage(Unknown Source) Looks like the MDB processing the message before Seam is initialized? This forces me to undeclare the SLSB as a Seam component and (potentially) duplicate business logic if I want to re-use the same functionality of the SLSB in Seam. I could use the solution from http://www.jboss.org/?module=bb&op=viewtopic&t=100946 but then it would force me to use vendor-specific API. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

13
22
0 / 0

[JBoss JIRA] (JBSEAM-5044) s:decorate javax.faces.FacesException: Cannot add the same component twice on Mojarra 2.1.11

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5044: ------------------------------------- Summary: s:decorate javax.faces.FacesException: Cannot add the same component twice on Mojarra 2.1.11 Key: JBSEAM-5044 URL: https://issues.jboss.org/browse/JBSEAM-5044 Project: Seam 2 Issue Type: Bug Components: JSF Controls Affects Versions: 2.3.0.Final Environment: AS 7.1.3.CR1 (Mojarra 2.1.11-jbossorg-3 20120815-1456) Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.1.CR1 s:decorate doesn't seem to work on new Mojarra 2.1.11, the following error is displayed while attempting to add invalide field message: {noformat} 17:13:28,175 SEVERE [org.richfaces.log.Context] (http-/127.0.0.1:8080-3) Cannot add the same component twice: register:nameDecorate:j_idt8: javax.faces.FacesException: Cannot add the same component twice: register:nameDecorate:j_idt8 at com.sun.faces.context.StateContext$AddRemoveListener.handleAddRemoveWithAutoPrune(StateContext.java:476) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.context.StateContext$AddRemoveListener.handleAdd(StateContext.java:422) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.context.StateContext$AddRemoveListener.processEvent(StateContext.java:338) [jsf-impl-2.1.11-jbossorg-3.jar:] at javax.faces.event.SystemEvent.processListener(SystemEvent.java:106) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at com.sun.faces.application.ApplicationImpl.processListenersAccountingForAdds(ApplicationImpl.java:2217) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.invokeViewListenersFor(ApplicationImpl.java:2038) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:291) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:246) [jsf-impl-2.1.11-jbossorg-3.jar:] at org.jboss.seam.jsf.SeamApplication.publishEvent(SeamApplication.java:452) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at javax.faces.component.UIComponentBase.publishAfterViewEvents(UIComponentBase.java:2201) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponentBase.doPostAddProcessing(UIComponentBase.java:1883) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponentBase.setParent(UIComponentBase.java:400) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at org.jboss.seam.ui.renderkit.DecorateRendererBase.doEncodeEnd(DecorateRendererBase.java:123) [jboss-seam-ui-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.ui.util.cdk.RendererBase.encodeEnd(RendererBase.java:104) [jboss-seam-ui-2.3.0.Final.jar:2.3.0.Final] at javax.faces.component.UIComponentBase.encodeEnd(UIComponentBase.java:875) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1786) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at org.richfaces.context.ExtendedPartialViewContextImpl$RenderVisitCallback.visit(ExtendedPartialViewContextImpl.java:504) [richfaces-core-impl-4.2.2.Final.jar:4.2.2.Final] at org.richfaces.context.BaseExtendedVisitContext.invokeVisitCallback(BaseExtendedVisitContext.java:321) [richfaces-core-impl-4.2.2.Final.jar:4.2.2.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1612) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIForm.visitTree(UIForm.java:371) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.visitTree(UIComponent.java:1623) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartialRenderPhase(ExtendedPartialViewContextImpl.java:272) [richfaces-core-impl-4.2.2.Final.jar:4.2.2.Final] at org.richfaces.context.ExtendedPartialViewContextImpl.processPartial(ExtendedPartialViewContextImpl.java:194) [richfaces-core-impl-4.2.2.Final.jar:4.2.2.Final] at javax.faces.component.UIViewRoot.encodeChildren(UIViewRoot.java:981) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1779) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at com.sun.faces.application.view.FaceletViewHandlingStrategy.renderView(FaceletViewHandlingStrategy.java:409) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.application.view.MultiViewHandler.renderView(MultiViewHandler.java:125) [jsf-impl-2.1.11-jbossorg-3.jar:] at org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:88) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:288) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:121) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101) [jsf-impl-2.1.11-jbossorg-3.jar:] at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.11-jbossorg-3.jar:] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.0.4.Final.jar:2.0.4.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam-2.3.0.Final.jar:2.3.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.17.Final.jar:] at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165) [jboss-as-web-7.1.3.CR1.jar:7.1.3.CR1] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.17.Final.jar:] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372) [jbossweb-7.0.17.Final.jar:] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.17.Final.jar:] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.17.Final.jar:] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.17.Final.jar:] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24] {noformat} -- 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

12 years, 3 months

1
3
0 / 0

[JBoss JIRA] (JBSEAM-4867) Run Seam 2.3 through the Seam 2 smoke tests

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4867: --------------------------------- Summary: Run Seam 2.3 through the Seam 2 smoke tests Key: JBSEAM-4867 URL: https://issues.jboss.org/browse/JBSEAM-4867 Project: Seam 2 Issue Type: Feature Request Reporter: Pete Muir Priority: Critical Fix For: 2.3.0.BETA1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

5
12
0 / 0

[JBoss JIRA] (JBSEAM-4871) Seam 2.3 Critical Path - describes key requirements for Seam 2.3

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4871: --------------------------------- Summary: Seam 2.3 Critical Path - describes key requirements for Seam 2.3 Key: JBSEAM-4871 URL: https://issues.jboss.org/browse/JBSEAM-4871 Project: Seam 2 Issue Type: Task Reporter: Pete Muir Assignee: Pete Muir Fix For: 2.3.0.Final -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[JBoss JIRA] (JBSEAM-5038) seam-gen generated project, editing ManyToOne relationship doesn't work

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5038: ------------------------------------- Summary: seam-gen generated project, editing ManyToOne relationship doesn't work Key: JBSEAM-5038 URL: https://issues.jboss.org/browse/JBSEAM-5038 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.CR1 Environment: MySQL 5, AS7.1.1 Reporter: Marek Schmidt Assignee: Marek Novotny Fix For: 2.3.0.Final Seam-gen generated project with two entities (Vehicle and Person) with a ManyToOne relationship doesn't work. Editing a "vehicle" and assigning a "person" doesn't seem to work. -- 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

12 years, 3 months

2
9
0 / 0

[JBoss JIRA] (JBSEAM-4878) Create migration guide from Seam 2.2 to Seam 2.3 for reference guide

by Pete Muir (JIRA)

Pete Muir created JBSEAM-4878: --------------------------------- Summary: Create migration guide from Seam 2.2 to Seam 2.3 for reference guide Key: JBSEAM-4878 URL: https://issues.jboss.org/browse/JBSEAM-4878 Project: Seam 2 Issue Type: Sub-task Reporter: Pete Muir -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

4
8
0 / 0

[JBoss JIRA] (JBSEAM-5030) Fix SeamTest getRenderedMailMessage to not use Renderer

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5030: ------------------------------------- Summary: Fix SeamTest getRenderedMailMessage to not use Renderer Key: JBSEAM-5030 URL: https://issues.jboss.org/browse/JBSEAM-5030 Project: Seam 2 Issue Type: Bug Components: Test Harness Affects Versions: 2.3.0.CR1 Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: 2.3.0.Final The Renderer requires properly initialized Mojarra, as it reads facelets via {code} ApplicationAssociate.getCurrentInstance().getFaceletFactory().getFacelet(url) {code} This is generally not available in a mock SeamTest environment. -- 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

12 years, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4320) Conversation propagation in SeamTest is broken.

by Arno Mittelbach (JIRA)

Conversation propagation in SeamTest is broken. ----------------------------------------------- Key: JBSEAM-4320 URL: https://jira.jboss.org/jira/browse/JBSEAM-4320 Project: Seam Issue Type: Bug Reporter: Arno Mittelbach Coversation propagation between FacesRequests in SeamTest is broken when redirects occur. If a conversation is started in a FacesRequest that ends with a redirect, this conversation cannot be restored in a consecutive FacesRequest. -- 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

12 years, 3 months

2
1
0 / 0

[JBoss JIRA] (JBSEAM-5043) Seam examples tests running from JBDS

by Marek Schmidt (JIRA)

Marek Schmidt created JBSEAM-5043: ------------------------------------- Summary: Seam examples tests running from JBDS Key: JBSEAM-5043 URL: https://issues.jboss.org/browse/JBSEAM-5043 Project: Seam 2 Issue Type: Feature Request Components: Examples Affects Versions: 2.3.0.Final Reporter: Marek Schmidt Assignee: Marek Schmidt Fix For: 2.3.1.CR1 Currently one has to run the maven "package" to produce the EAR before running the tests. Test deployments should be changed not to depend on the maven package => use shrinkwrap dependency resolver for dependencies and package test jar manually in shrinkwrap. -- 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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5042) Seam-gen EAR generated project wrong comments in web.xml

by Tomas Remes (JIRA)

Tomas Remes created JBSEAM-5042: ----------------------------------- Summary: Seam-gen EAR generated project wrong comments in web.xml Key: JBSEAM-5042 URL: https://issues.jboss.org/browse/JBSEAM-5042 Project: Seam 2 Issue Type: Bug Components: Tools Affects Versions: 2.3.0.CR1 Reporter: Tomas Remes Fix For: 2.3.0.Final There is wrong usage of comments in WEB-INF/web.xml in EAR project generated by Seam-gen. The closing tag for web-app is commented. {noformat} </web-app>--> {noformat} -- 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

12 years, 3 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2012