November 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4673) java.lang.IllegalStateException: No active event context for tasks example after each request

by Gaël Beaudoin (JIRA)

java.lang.IllegalStateException: No active event context for tasks example after each request --------------------------------------------------------------------------------------------- Key: JBSEAM-4673 URL: https://jira.jboss.org/browse/JBSEAM-4673 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.2.1.CR1 Environment: JBoss 4.2.3 Seam 2.2.1-SNAPSHOT Reporter: Gaël Beaudoin When logged in, this error is thrown during each request : 14:50:47,597 ERROR [Exceptions] handled and logged exception javax.servlet.ServletException: java.lang.IllegalStateException: No active event context at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:75) at org.jboss.seam.web.AuthenticationFilter.doFilter(AuthenticationFilter.java:120) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:182) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262) at org.apache.coyote.ajp.AjpAprProcessor.process(AjpAprProcessor.java:419) at org.apache.coyote.ajp.AjpAprProtocol$AjpConnectionHandler.process(AjpAprProtocol.java:378) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1508) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalStateException: No active event context at org.jboss.seam.core.Manager.instance(Manager.java:368) at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:56) ... 29 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMREST-3) Support templating using Facelets

by Jozef Hartinger (JIRA)

Support templating using Facelets --------------------------------- Key: SEAMREST-3 URL: https://jira.jboss.org/browse/SEAMREST-3 Project: Seam RESTEasy Issue Type: Feature Request Reporter: Jozef Hartinger Fix For: Alpha2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMREST-5) Provide integration with RESTEasy Client Framework

by Jozef Hartinger (JIRA)

Provide integration with RESTEasy Client Framework -------------------------------------------------- Key: SEAMREST-5 URL: https://jira.jboss.org/browse/SEAMREST-5 Project: Seam REST Issue Type: Feature Request Components: Client Affects Versions: Alpha2 Reporter: Jozef Hartinger Assignee: Jozef Hartinger Provide an easy way to access remote REST-based web services. This extension is optional (activated only when RESTEasy is on classpath) http://docs.jboss.org/resteasy/docs/2.0.0.GA/userguide/html/RESTEasy_Clie... @Inject @RestService(url="...") private ClientRequest request; @Inject @RestService(url="...") private UserService users; As part of this issue, it is necessary to overhaul the seam-rest.jar not to be a BDA (to aviod CNFE in non-RESTEasy environment) and register the beans through extensions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-909) RCFaces compatibility

by Daniel Wiell (JIRA)

RCFaces compatibility --------------------- Key: JBSEAM-909 URL: http://jira.jboss.com/jira/browse/JBSEAM-909 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.6.GA Environment: JBoss Seam 1.1.6, JSF 1.1 RI (or MyFaces 1.1.5), Facelets 1.1.11, RCFaces 1.0b3 (or nightly from 20070221), Tomcat 5.5.20 Reporter: Daniel Wiell 1. Download RCFaces-facelets-starter-kit-v1-0b3.war (http://downloads.sourceforge.net/rcfaces/RCFaces-facelets-starter-kit-v1-...). 2. Deploy it in Tomcat. 3. Try the app - sorting the table works fine. 4. Build the "hibernate" example in Seam 1.1.6. 5. Copy over the jar files from the hibernate webapp to the "RCFaces-facelets-starter-kit" webapp, excluding the MyFaces jars and removing any dublicates. 6. Add "SeamListener" and "Seam Redirect Filter" to web.xml. 7. Add "SeamPhaseListener" to faces-config.xml. 8. Copy the components.xml and remove "bookingDatabase". 8. Redeploy the app. 9. Try it - when sorting you get the following stacktrace: java.lang.IllegalStateException: No phase id bound to current thread (make sure you do not have two SeamPhaseListener instances installed) at org.jboss.seam.contexts.PageContext.getPhaseId(PageContext.java:153) at org.jboss.seam.contexts.PageContext.isRenderResponsePhase(PageContext.java:165) at org.jboss.seam.contexts.PageContext.getCurrentReadableMap(PageContext.java:76) at org.jboss.seam.contexts.PageContext.get(PageContext.java:66) at org.jboss.seam.contexts.Contexts.lookupInStatefulContexts(Contexts.java:160) at org.jboss.seam.Component.getInstance(Component.java:1635) at org.jboss.seam.jsf.SeamVariableResolver.resolveVariable(SeamVariableResolver.java:53) at com.sun.facelets.el.LegacyELContext$LegacyELResolver.getValue(LegacyELContext.java:134) at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:65) at com.sun.el.parser.AstValue.getValue(AstValue.java:106) at com.sun.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:192) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) at com.sun.facelets.el.LegacyValueBinding.getValue(LegacyValueBinding.java:56) at org.rcfaces.core.internal.component.BasicComponentEngine.getInternalProperty(BasicComponentEngine.java:149) at org.rcfaces.core.internal.component.BasicComponentEngine.getValue(BasicComponentEngine.java:402) at org.rcfaces.core.internal.component.CameliaGridComponent.getValue(CameliaGridComponent.java:418) at org.rcfaces.core.internal.component.CameliaGridComponent.getDataModel(CameliaGridComponent.java:401) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer$TableRenderContext.<init>(DataGridRenderer.java:2624) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer$TableRenderContext.<init>(DataGridRenderer.java:2691) at org.rcfaces.renderkit.html.internal.renderer.DataGridRenderer.createTableContext(DataGridRenderer.java:677) at org.rcfaces.renderkit.html.internal.service.DataGridService.writeJs(DataGridService.java:242) at org.rcfaces.renderkit.html.internal.service.DataGridService.service(DataGridService.java:171) at org.rcfaces.core.internal.config.ServicesRegistryImpl.afterPhase(ServicesRegistryImpl.java:121) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:254) at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:110) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:213) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.seam.servlet.SeamRedirectFilter.doFilter(SeamRedirectFilter.java:29) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:432) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) 10. Comment out the "SeamPhaseListener" and retry - now it works again. It's too bad, since RCFaces seems like a really great component library. -- 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

13 years, 7 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2849) Initialization warning about PojoCache could be changed/removed

by Jay Balunas (JIRA)

Initialization warning about PojoCache could be changed/removed --------------------------------------------------------------- Key: JBSEAM-2849 URL: http://jira.jboss.com/jira/browse/JBSEAM-2849 Project: JBoss Seam Issue Type: Task Affects Versions: 2.0.2.CR1 Reporter: Jay Balunas Priority: Optional When Seam starts up it shows this message : WARN [Initialization] Did not install PojoCache due to NoClassDefFoundError: org/jgroups/MembershipListener it has been there a very long time (as far as I can tell). It originates in the below code snip. Is this something we can remove or change to "debug"? It causes no problems, but might confuse. Initialization.java: catch (NoClassDefFoundError e) { //temp solution due to broken JEMS installer portal profile! log.warn("Did not install PojoCache due to NoClassDefFoundError: " + e.getMessage()); } -- 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

13 years, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3124) How to produce: No active JTA transaction on joinTransaction call

by Terry (JIRA)

How to produce: No active JTA transaction on joinTransaction call ----------------------------------------------------------------- Key: JBSEAM-3124 URL: http://jira.jboss.com/jira/browse/JBSEAM-3124 Project: Seam Issue Type: Quality Risk Components: Core Affects Versions: 2.0.1.GA Environment: JBoss 4.2EAP, Faceslets Reporter: Terry Priority: Optional Fix For: The future Following unrelated exception is thrown, if in EntityQuery extented class, there is a space in # and { or EL of Restrictions list. eg, private static final String[] RESTRICTIONS = { "lower(orgCampus.id) = # {courseSysCourseList.selectedOrgCampusIdConverted}", "lower(org.id) = #{courseSysCourseList.selectedOrgIdConverted}", } Caused by: javax.persistence.TransactionRequiredException: No active JTA transaction on joinTransaction call at org.hibernate.ejb.AbstractEntityManagerImpl.joinTransaction(AbstractEntityManagerImpl.java:469) at org.hibernate.ejb.AbstractEntityManagerImpl.joinTransaction(AbstractEntityManagerImpl.java:442) at org.jboss.seam.persistence.EntityManagerProxy.joinTransaction(EntityManagerProxy.java:120) at org.jboss.seam.transaction.AbstractUserTransaction.enlist(AbstractUserTransaction.java:73) at org.jboss.seam.framework.EntityQuery.joinTransaction(EntityQuery.java:230) Perhaps a more appropriate exception would be helpful in this instance. -- 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

13 years, 7 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3387) Pages.xsd - Page element's scheme attribute use enum of http and https

by Arron Ferguson (JIRA)

Pages.xsd - Page element's scheme attribute use enum of http and https ---------------------------------------------------------------------- Key: JBSEAM-3387 URL: https://jira.jboss.org/jira/browse/JBSEAM-3387 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.BETA1 Environment: N/A Reporter: Arron Ferguson Priority: Optional Currently the pages.xml file has the following page element's scheme attribute defined as: <xs:attribute name="scheme"/> Since the user will be using one of two protocols: http or https, the scheme attribute should have: <xs:attribute name="scheme" default="false"> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value="http"/> <xs:enumeration value="https"/> </xs:restriction> </xs:simpleType> </xs:attribute> -- 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

13 years, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3828) Seam GWT servlet should no longer use deprecated SerializableException

by Jan Vorwerk (JIRA)

Seam GWT servlet should no longer use deprecated SerializableException ---------------------------------------------------------------------- Key: JBSEAM-3828 URL: https://jira.jboss.org/jira/browse/JBSEAM-3828 Project: Seam Issue Type: Patch Components: GWT Reporter: Jan Vorwerk Priority: Optional Since GWT 1.5 the usage of SerializableException has been deprecated, while Seam Remoting servlet for GWT compells its usage as a base class for serializable exceptions to be marshalled from the server to the client. See code in: org.jboss.seam.remoting.gwt.GWTService#processCall(String) // Serialize the exception back to the client if it's a declared // exception if (cause instanceof SerializableException) -- 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

13 years, 7 months

2
1
0 / 0

[JBoss JIRA] Updated: (SEAMCATCH-12) Add ExceptionResponse to the API

by Jason Porter (JIRA)

[ https://jira.jboss.org/browse/SEAMCATCH-12?page=com.atlassian.jira.plugin... ] Jason Porter updated SEAMCATCH-12: ---------------------------------- Fix Version/s: Alpha2 (was: Alpha1) > Add ExceptionResponse to the API > -------------------------------- > > Key: SEAMCATCH-12 > URL: https://jira.jboss.org/browse/SEAMCATCH-12 > Project: Seam Catch > Issue Type: Feature Request > Affects Versions: Alpha1 > Reporter: Dan Allen > Assignee: Jason Porter > Priority: Minor > Fix For: Alpha2 > > > Add a reusable ExceptionResponse value object to the API for use in specifying exception to HTTP responses. This will likely get reused by the JAX-RS, Servlet and JSF integrations, at the very least. > ExceptionResponse { > forType > statusCode > message > logLevel? > } > A similar API was introduced in the REST module alpha. I'd like to consolidate such classes. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMCATCH-9) @HandlesExceptions annotation should not be a qualifier

by Jason Porter (JIRA)

[ https://jira.jboss.org/browse/SEAMCATCH-9?page=com.atlassian.jira.plugin.... ] Jason Porter updated SEAMCATCH-9: --------------------------------- Fix Version/s: Alpha2 (was: Beta1) > @HandlesExceptions annotation should not be a qualifier > ------------------------------------------------------- > > Key: SEAMCATCH-9 > URL: https://jira.jboss.org/browse/SEAMCATCH-9 > Project: Seam Catch > Issue Type: Bug > Affects Versions: Alpha1 > Reporter: Dan Allen > Assignee: Dan Allen > Fix For: Alpha2 > > > @HandlesExceptions should simply be marker annotation, not a qualifier. Treating it as a qualifier changes the behavior of the bean to which it's applied, which is not want we want. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 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 November 2010