December 2008 - seam-issues - Jboss List Archives

[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, 5 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, 5 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, 5 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, 5 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, 5 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3247) Seam without hibernate: Please make org.jboss.seam.core.Validators independent from Hibernate

by Francisco Jose Peredo Noguez (JIRA)

Seam without hibernate: Please make org.jboss.seam.core.Validators independent from Hibernate ---------------------------------------------------------------------------------------------- Key: JBSEAM-3247 URL: https://jira.jboss.org/jira/browse/JBSEAM-3247 Project: Seam Issue Type: Feature Request Affects Versions: 2.0.2.GA Reporter: Francisco Jose Peredo Noguez I think org.jboss.seam.core.Validators should implement and interface, so that it could be possible to replace it with one that doesn't use org.hibernate.validator.ClassValidator I guess with that we could say that Seam can be used in a 100% free of Hibernate way I really like Hibernate, but sometimes, for really simple projects, or for projects full of interactions with stored procedures , it might be overkill or innapropiate, so it would be nice to be able to use Seam without having any Hibernate dependencies. -- 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, 5 months

5
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3706) JEE5 Booking Example fails on Glassfish

by Dmitry Shultz (JIRA)

JEE5 Booking Example fails on Glassfish --------------------------------------- Key: JBSEAM-3706 URL: https://jira.jboss.org/jira/browse/JBSEAM-3706 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.0.SP1 Environment: Leopard OS X Server, latest Glassfish installation (9.1_02 (build b04-fcs)), Seam version from todays trunk. Reporter: Dmitry Shultz Priority: Blocker 1. Buld Seam, build JEE5 Booking Example, deploy it on Glassfish using Web Interface. 2. Create new User, do login 3. Go to the Search Hotels page, put letter 'd' in the input field, press Find Hotels 4. Click on 'View Hotel' Link for top hotel, you should see the seam.debug page. -- 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, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3006) web:character-encoding-filter and UTF-8 not working

by Bruno Orcha Garcￃﾭa (JIRA)

web:character-encoding-filter and UTF-8 not working ---------------------------------------------------- Key: JBSEAM-3006 URL: http://jira.jboss.com/jira/browse/JBSEAM-3006 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Reporter: Bruno Orcha Garcￃﾭa web:character-encoding-filter is not working. When submitting UTF-8 characters in a h:inputText (for example), the string contains invalid characters, due a bad encoding interpretation. This issue should be fixed configuring the web:character-encoding-filter to UTF-8 in component.xml, but this is not working. This filter should be the first, in the seam filter stack?. Using a filter in web.xml it's the unique solution that works currently. -- 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, 6 months

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1839) Use HSQL to store Quartz jobs when deployed on JBoss AS

by Michael Yuan (JIRA)

Use HSQL to store Quartz jobs when deployed on JBoss AS ------------------------------------------------------- Key: JBSEAM-1839 URL: http://jira.jboss.com/jira/browse/JBSEAM-1839 Project: JBoss Seam Issue Type: Feature Request Reporter: Michael Yuan Assigned To: Michael Yuan Fix For: 2.0.0.GA Right now, Quartz jobs are stored "in-memory" and hence cannot be auto-started when the server reboots. The user can use persistence job stores by using a custom quartz property file. However, in JBoss AS, we should store jobs in the HSQL DB by default: * In the dispatcher component, we can have a "jboss=true" attribute * If this attribute is true, the QuartzDispatcher will setup Quartz tables for this particular app in the HSQL at startup, and then use the HSQL DB as persistent job store. This way, when the application deploys again, all the jobs for this application will be auto-started again. -- 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, 6 months

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2353) Quartz asynchronous events shceduled to fire while the server is shutdown fire before seam is initialized when the server is started.

by Yona Appletree (JIRA)

Quartz asynchronous events shceduled to fire while the server is shutdown fire before seam is initialized when the server is started. ------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2353 URL: http://jira.jboss.com/jira/browse/JBSEAM-2353 Project: JBoss Seam Issue Type: Bug Components: Async Environment: Jboss 4.2.2.GA; Quartz scheduler. Reporter: Yona Appletree Fix For: 2.0.0.GA When the QuartzDispatcher is created, it causes any event scheduled to fire in the past to fire immediately (in a separate thread). Since QuartzDispatcher is marked @Startup, it may start before other components. If the handler of an event fired on startup relies on another component marked @Startup, it may not exist by the time the event is fired, and will therefore cause an error. I have a found a partial workaround for this issue, documented in the referenced forum thread. -- 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, 6 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008