December 2010 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (JBSEAM-4737) Change default persistence service configuration for jBPM

by Martin Putz (JIRA)

Change default persistence service configuration for jBPM --------------------------------------------------------- Key: JBSEAM-4737 URL: https://jira.jboss.org/browse/JBSEAM-4737 Project: Seam Issue Type: Task Components: BPM Affects Versions: 2.2.1.CR2 Reporter: Martin Putz With the newer jBPM jars, it is recommended to use the following configuration for the persistence service: <service name="persistence"> <factory> <bean class="org.jbpm.persistence.jta.JtaDbPersistenceServiceFactory"> <property name="currentSessionEnabled"><false /></property> </bean> </factory> </service> With JtaDbPersistenceService, transactions are disabled by default, the "current" Hibernate session is enabled, the JTA transaction status is queried directly, and reported correctly to jBPM components such as GraphElement.isAbleToHandleExceptions. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-18) Provide convenient access to include and forward request parameters

by Dan Allen (JIRA)

Provide convenient access to include and forward request parameters ------------------------------------------------------------------- Key: SEAMSERVLET-18 URL: https://jira.jboss.org/browse/SEAMSERVLET-18 Project: Seam Servlet Issue Type: Feature Request Components: Utilities Affects Versions: 3.0.0.Alpha1 Reporter: Dan Allen During an include or forward, vital information gets stuffed into request parameters. It would be nice to be able to access this information from an injectable Java resource. javax.servlet.forward.request_uri javax.servlet.forward.context_path javax.servlet.forward.servlet_path javax.servlet.forward.path_info javax.servlet.forward.query_string javax.servlet.include.request_uri javax.servlet.include.context_path javax.servlet.include.servlet_path javax.servlet.include.path_info javax.servlet.include.query_string -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (SEAMSERVLET-16) Provide a more convenient solution for welcome pages

by Dan Allen (JIRA)

Provide a more convenient solution for welcome pages ---------------------------------------------------- Key: SEAMSERVLET-16 URL: https://jira.jboss.org/browse/SEAMSERVLET-16 Project: Seam Servlet Issue Type: Feature Request Affects Versions: 3.0.0.Alpha1 Reporter: Dan Allen Priority: Minor Provide a more convenient way of doing welcome pages instead of having to configure web.xml. This will address limitations of using index.jsf as a welcome page (which doesn't work in JBoss AS). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Updated: (SEAMSERVLET-9) Include conversations based off of the application context, not only the session context

by Dan Allen (JIRA)

[ https://jira.jboss.org/browse/SEAMSERVLET-9?page=com.atlassian.jira.plugi... ] Dan Allen updated SEAMSERVLET-9: -------------------------------- Component/s: Conversations > Include conversations based off of the application context, not only the session context > ---------------------------------------------------------------------------------------- > > Key: SEAMSERVLET-9 > URL: https://jira.jboss.org/browse/SEAMSERVLET-9 > Project: Seam Servlet > Issue Type: Feature Request > Components: Conversations > Reporter: Dan Hinojosa > Priority: Minor > Labels: Application, Application_Context, Conversation, Conversations, ServletContext, Servlet_Context > > Pete and I just got done going through this, and he asked me to place this in for review. The use case that I mentioned was " Real time multi-user chat with multiple conversations" My intention was this would be a great solution for web apps that do not want to go through JMS to design something so simple. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Updated: (SEAMSERVLET-8) Conversation are only for JSF: Please make then available for plain servlets and JSP

by Dan Allen (JIRA)

[ https://jira.jboss.org/browse/SEAMSERVLET-8?page=com.atlassian.jira.plugi... ] Dan Allen updated SEAMSERVLET-8: -------------------------------- Component/s: Conversations > Conversation are only for JSF: Please make then available for plain servlets and JSP > ------------------------------------------------------------------------------------ > > Key: SEAMSERVLET-8 > URL: https://jira.jboss.org/browse/SEAMSERVLET-8 > Project: Seam Servlet > Issue Type: Feature Request > Components: Conversations > Reporter: Francisco Jose Peredo Noguez > Priority: Optional > > Aacording to Weld the docs: > The conversation context is active during any JSF request. > and at the code of org.jboss.weld.servlet.ConversationPropagationFilter > One can read > FIXME This filter is specifically for JSF and should be repackaged or split up to support non-JSF environments. > All that indicates that conversations are only for JSF. Please make them available for plain servlets (and JSPs) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
0
0 / 0

[JBoss JIRA] Commented: (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 commented on SEAMCATCH-12: --------------------------------------- Hm, okay, so we're thinking of leaving this out for right now? It's probably easier if all the info is in the object than split between the object and the qualifiers, but may not. > 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

14 years, 1 month

1
0
0 / 0

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

by Dan Allen (JIRA)

[ https://jira.jboss.org/browse/SEAMCATCH-12?page=com.atlassian.jira.plugin... ] Dan Allen commented on SEAMCATCH-12: ------------------------------------ Perhaps we can leave off level in the first cut. I suggested it since it was something that Seam 2's exception mapping config offered. But that was a hard-coded behavior. We also need to recommend how exception mappings are filtered by request type (may just be a docs issue). It could be a qualifier that is added to the type in the XML config (as opposed to a field on ExceptionResponse). One of the key features of Seam Catch over the exception handling in Seam 2 is that we are factoring into the design how to use different mappings for different types of requests (or scenarios in general). > 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

14 years, 1 month

1
0
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

14 years, 1 month

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

14 years, 1 month

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

14 years, 1 month

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2010