May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1144) Make org.jboss.seam.util.Transactions a seam component

by Michael Youngstrom (JIRA)

Make org.jboss.seam.util.Transactions a seam component ------------------------------------------------------ Key: JBSEAM-1144 URL: http://jira.jboss.com/jira/browse/JBSEAM-1144 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Fix For: 1.3.0.BETA1 I know this is probably a loaded issue but please hear me out. :) It would be nice if org.jboss.seam.util.Transactions was replaced with a Seam Component just like everything else in Seam. This would allow for pluggable Transaction Management providers and pave the way for support for Spring Managed Transactions, JPA Local Transactions, and true Hibernate Local Transactions. This will allow Seam applications to run without a dependency on microcontainer in tomcat and allow for tighter Framework integration with spring and others. I would personally be more than willing to do the work of making the an initial JTATransaction component(s) as a replacement for org.jboss.seam.util.Transactions and would also create a SpringTransaction component as a proof of concept for extending the Transaction component. One problem I can see off hand is we may have to interact with a transaction in some places where a Seam ApplicationContext is not available. However, I wonder if confining Seam transactions to a seam call might help simplify matters anyway? For example transaction cleanup could take place in the @Destroy of the transaction component instead of in the ExceptionFilter? Also, this wouldn't be looked at as a JTA replacement but rather a service abstraction. Just like any other java webapp if you're using enterprise services such as EJBs or JCA JTA would be required. if you're running on tomcat or some other simple web container a resource local transaction manager (Spring's abstraction, JPA's, or Hibernate's) can be used. I'm sure there are tons of other problems I'm not looking at but worst case scenario this issue would be a great place to document them and to refer rejected feature requests. (for example JBSEAM-1118) What do you think? Mike -- 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

17 years, 8 months

5
24
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1369) Startup error: could not instantiate Seam component: org.jboss.seam.security.identity

by Hung Tang (JIRA)

Startup error: could not instantiate Seam component: org.jboss.seam.security.identity ------------------------------------------------------------------------------------- Key: JBSEAM-1369 URL: http://jira.jboss.com/jira/browse/JBSEAM-1369 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 1.3.0.ALPHA Reporter: Hung Tang This issue is difficult to re-produce and only happens during every 50 or so restarts. It occurs when I first access my home page after restarting JBoss App. I thought I would enter it in JIRA if the problem looks familiar and is fixable from inspection. It goes away after doing another restart. SEVERE: Error Rendering View[/home.xhtml] org.jboss.seam.InstantiationException: Could not instantiate Seam component: org .jboss.seam.security.identity at org.jboss.seam.Component.newInstance(Component.java:1744) at org.jboss.seam.Component.getInstance(Component.java:1647) at org.jboss.seam.Component.getInstance(Component.java:1614) at org.jboss.seam.Namespace.get(Namespace.java:42) at javax.el.MapELResolver.getValue(MapELResolver.java:51) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELRe solver.java:64) at org.jboss.el.parser.AstPropertySuffix.getValue(AstPropertySuffix.java :53) at org.jboss.el.parser.AstValue.getValue(AstValue.java:67) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:18 6) at org.jboss.seam.core.Expressions$1.getValue(Expressions.java:82) at org.jboss.seam.Component.getInstanceFromFactory(Component.java:1688) at org.jboss.seam.Component.getInstance(Component.java:1637) at org.jboss.seam.Component.getInstance(Component.java:1614) at org.jboss.seam.Component.getInstance(Component.java:1608) at org.jboss.seam.el.SeamELResolver.getValue(SeamELResolver.java:57) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53) at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELRe solver.java:64) at org.jboss.el.parser.AstIdentifier.getValue(AstIdentifier.java:44) at org.jboss.el.parser.AstValue.getValue(AstValue.java:63) at org.jboss.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:18 6) at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.ja va:71) at javax.faces.component.UIComponentBase.isRendered(UIComponentBase.java :370) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:880) at javax.faces.component.UIComponent.encodeAll(UIComponent.java:892) at com.sun.facelets.FaceletViewHandler.renderView(FaceletViewHandler.jav a:571) at org.ajax4jsf.framework.ViewHandlerWrapper.renderView(ViewHandlerWrapp er.java:108) at org.ajax4jsf.framework.ajax.AjaxViewHandler.renderView(AjaxViewHandle r.java:232) at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePha se.java:106) at com.sun.faces.lifecycle.LifecycleImpl.phase(LifecycleImpl.java:251) at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:144) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:245) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:69) at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:59) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:55) at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:47) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:55) at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:81) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:55) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:59) at org.ajax4jsf.framework.ajax.xmlfilter.BaseXMLFilter.doXmlFilter(BaseX MLFilter.java:126) at org.ajax4jsf.framework.ajax.xmlfilter.BaseFilter.doFilter(BaseFilter. java:248) at org.jboss.seam.web.AbstractAjax4jsfFilter.doFilter(AbstractAjax4jsfFi lter.java:35) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:55) at org.jboss.seam.debug.hot.HotDeployFilter.doFilter(HotDeployFilter.jav a:64) at org.jboss.seam.web.SeamFilter$FilterChainImpl.doFilter(SeamFilter.jav a:55) at org.jboss.seam.web.SeamFilter.doFilter(SeamFilter.java:126) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFi lter.java:96) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl icationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF ilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV alve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV alve.java:175) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(Securit yAssociationValve.java:179) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(Authentica torBase.java:433) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv e.java:84) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j ava:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j ava:104) at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC onnectionValve.java:156) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal ve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav a:241) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java :844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce ss(Http11Protocol.java:580) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44 7) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.IllegalArgumentException: could not set property value: org .jboss.seam.security.identity.setSecurityRules at org.jboss.seam.Component.setPropertyValue(Component.java:1551) at org.jboss.seam.Component.initialize(Component.java:1177) at org.jboss.seam.Component.instantiateJavaBean(Component.java:1136) at org.jboss.seam.Component.instantiate(Component.java:1089) at org.jboss.seam.Component.newInstance(Component.java:1740) ... 67 more Caused by: java.lang.IllegalArgumentException: Could not invoke method by reflec tion: RuleBasedIdentity.setSecurityRules(org.drools.RuleBase) with parameters: ( org.jboss.seam.drools.RuleBase) on: org.jboss.seam.security.RuleBasedIdentity at org.jboss.seam.util.Reflections.invoke(Reflections.java:31) at org.jboss.seam.Component.setPropertyValue(Component.java:1547) ... 71 more Caused by: java.lang.IllegalArgumentException: argument type mismatch at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.seam.util.Reflections.invoke(Reflections.java:21) ... 72 more -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1128) Calling getPage outside of a JSF request causes NPE

by Mike Quilleash (JIRA)

Calling getPage outside of a JSF request causes NPE --------------------------------------------------- Key: JBSEAM-1128 URL: http://jira.jboss.com/jira/browse/JBSEAM-1128 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash During Seam startup I have a component that scans installed components and programatically builds page entries (page actions etc). I use getPage() as this returns a new blank page if the. However calling getPage() outside of a JSF request throws NPE as Pages.getSuffix() calls FacesContext.getCurrentInstance().getExternalContext().getInitParameter(ViewHandler.DEFAULT_SUFFIX_PARAM_NAME); The check in my case is unnecessary (the comment mentions something about a bug in the JSF RI, I am using RI 1.2_02) as the view id already has the correct suffix. -- 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

17 years, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-197) Order task list by priority

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-197?page=all ] Gavin King updated JBSEAM-197: ------------------------------ Fix Version/s: 1.3.0.ALPHA (was: 1.3.0.BETA1) Assignee: Gavin King > Order task list by priority > --------------------------- > > Key: JBSEAM-197 > URL: http://jira.jboss.com/jira/browse/JBSEAM-197 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > Priority: Minor > Fix For: 1.3.0.ALPHA > > > Should make it possible to sort the tasks in the task list by priority. -- 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

17 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-382) TaskConversationContext or TASK scope

by Gavin King (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-382?page=all ] Gavin King updated JBSEAM-382: ------------------------------ Fix Version/s: (was: 1.3.0.BETA1) > TaskConversationContext or TASK scope > ------------------------------------- > > Key: JBSEAM-382 > URL: http://jira.jboss.com/jira/browse/JBSEAM-382 > Project: JBoss Seam > Issue Type: Feature Request > Components: BPM > Reporter: Gavin King > Assigned To: Gavin King > > We could support an alternative implementation of the conversation Context where variables get saved not to the HttpSession but to the jBPM database. > This would mean that the work in progress could be recovered by the user. > Alternatively, we could have a special TASK context. -- 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

17 years, 8 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1315) Scheduled methods doesn't incjet Strings from app properties.

by Stateless Bean (JIRA)

Scheduled methods doesn't incjet Strings from app properties. ------------------------------------------------------------- Key: JBSEAM-1315 URL: http://jira.jboss.com/jira/browse/JBSEAM-1315 Project: JBoss Seam Issue Type: Bug Components: Examples Affects Versions: 1.2.1.GA Environment: Win XP Home, JBoss AS 4.0.5, PostgreSql 8.2, EJB 3.0, Seam 1.2.1 Reporter: Stateless Bean Fix For: 1.3.0.BETA1 Messages instance incjected like: @In protected Map<String, String> messages; doesn't work in scheduled method. I got app properties file like "login.password = blabla,bleble, bububububu" and i still get "login.password" instead of "blabla...". This problem exist even in seampay example. Messages works fine without scheduled methods. -- 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

17 years, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1286) Add Event notifications to Exceptions component

by Chris Rudd (JIRA)

Add Event notifications to Exceptions component ----------------------------------------------- Key: JBSEAM-1286 URL: http://jira.jboss.com/jira/browse/JBSEAM-1286 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Rudd Add Event notifications to the Exception handling system so that components can listen for exceptions and do additional actions. This would allow an end users development of a solution for JBSEAM-1285 using the same concept that is employed in the existing Login Redirection functionality. -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1285) Expose originating view in conversation for exception handling.

by Chris Rudd (JIRA)

Expose originating view in conversation for exception handling. --------------------------------------------------------------- Key: JBSEAM-1285 URL: http://jira.jboss.com/jira/browse/JBSEAM-1285 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Rudd Currently the exception handling system exposes the exception so that the redirected to page can report it if needed. It would be nice if the oridinating view / request parameters were also exposed. This would allow the exception report to provide a back link to take you back to the area you were working on. -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1284) Expose an addHandler method in Exceptions component

by Chris Rudd (JIRA)

Expose an addHandler method in Exceptions component --------------------------------------------------- Key: JBSEAM-1284 URL: http://jira.jboss.com/jira/browse/JBSEAM-1284 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Chris Rudd Expose an addHandler method on the Exceptions component so that you can programatically add handlers. Optionally expose it as a protected method so that someone can extend the Exceptions component so that exceptions handlers defined in alternate locations can be added to the component. -- 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

17 years, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1340) EntityManager is not injected in jpa example from ajax4j requests

by Anastasios Georgousakis (JIRA)

EntityManager is not injected in jpa example from ajax4j requests ----------------------------------------------------------------- Key: JBSEAM-1340 URL: http://jira.jboss.com/jira/browse/JBSEAM-1340 Project: JBoss Seam Issue Type: Bug Components: Core, Examples Affects Versions: 1.3.0.BETA1 Environment: WindowsXP, JBoss 4.2.0.GA, jboss-seam-CVS.20070519 Reporter: Anastasios Georgousakis I tried to run the examples from the latest snapshot (jboss-seam-CVS.20070519) and I saw that the examples not using EJB container like jpa does not run properly in Jboss 4.2.0.GA. When an ajax4j request is made (e.g. when you press a chanracter in the to search input field) the following exception is throwed Exception during request processing: Caused by javax.servlet.ServletException with message: "/main.xhtml @22,94 value="#{hotelSearch.searchString}": Error reading 'searchString' on type org.jboss.seam.example.jpa.HotelSearchingAction_$$_javassist_9" Caused by javax.el.ELException with message: "/main.xhtml @22,94 value="#{hotelSearch.searchString}": Error reading 'searchString' on type org.jboss.seam.example.jpa.HotelSearchingAction_$$_javassist_9" Caused by org.jboss.seam.RequiredException with message: "In attribute requires non-null value: hotelSearch.entityManager" -- 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

17 years, 8 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007