May 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1130) Upgrade to jBPM 3.2

by Gavin King (JIRA)

Upgrade to jBPM 3.2 ------------------- Key: JBSEAM-1130 URL: http://jira.jboss.com/jira/browse/JBSEAM-1130 Project: JBoss Seam Issue Type: Task Components: BPM Reporter: Gavin King Priority: Critical Fix For: 1.3.0.BETA1 -- 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

18 years, 9 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1330) Cant use EL expressions for pdf colors

by Dustin Norlander (JIRA)

Cant use EL expressions for pdf colors -------------------------------------- Key: JBSEAM-1330 URL: http://jira.jboss.com/jira/browse/JBSEAM-1330 Project: JBoss Seam Issue Type: Bug Components: PDF Reporter: Dustin Norlander Using el expressions for color values in pdf generation fails with classcast exception. Problem is that the valueBinding expects a Color but gets a String.. UIRectange.java public void applyRectangleProperties(FacesContext context, Rectangle rectangle) { .... backgroundColor = (Color)valueBinding(context, "backgroundColor", backgroundColor); if (backgroundColor != null) { rectangle.setBackgroundColor(backgroundColor); } .... ect ... -- 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

18 years, 9 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1321) Could possibly remove the requirement to specify SeamListener in web.xml

by Mike Quilleash (JIRA)

Could possibly remove the requirement to specify SeamListener in web.xml ------------------------------------------------------------------------ Key: JBSEAM-1321 URL: http://jira.jboss.com/jira/browse/JBSEAM-1321 Project: JBoss Seam Issue Type: Task Components: Core Affects Versions: 1.2.1.GA Environment: Tomcat 6 Reporter: Mike Quilleash I noticed the the JSF RI 1.2 uses a trick to avoid having to specify the <listener> explicitly in web.xml. It has a .tld file in the META-INF directory of the implementation jar. This gets scanned by the web container (Tomcat 6 in this case) and any <listener> in the file get executed. <listener> <listener-class>com.sun.faces.config.ConfigureListener</listener-class> </listener> Maybe Seam could do something similar in the main seam jar. As this is a tld I guess it's relying on the JSP spec, what version this listener was introduced in I'm not sure, but I guess all JEE5 implementations should support this. -- 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

18 years, 9 months

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1355) ConverterChain.getAsString behaves incorrectly if the input is String already

by Sergey Koshcheyev (JIRA)

ConverterChain.getAsString behaves incorrectly if the input is String already ----------------------------------------------------------------------------- Key: JBSEAM-1355 URL: http://jira.jboss.com/jira/browse/JBSEAM-1355 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.1.GA Reporter: Sergey Koshcheyev ConverterChain.getAsString(FacesContext context, UIComponent component, Object value) will return null if value is String already. It should cast the value to String and return that instead. Proposed fix: change String output = null; to String output = value instanceof String ? (String) value : null; This happens when UIComponent.value is bound to a String property. In this case no "final" converter will be added to the chain, so output will be null after the loop in getAsString. -- 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

18 years, 9 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1377) provide dispatcher for Spring TaskExecutor abstraction

by Michael Youngstrom (JIRA)

provide dispatcher for Spring TaskExecutor abstraction ------------------------------------------------------ Key: JBSEAM-1377 URL: http://jira.jboss.com/jira/browse/JBSEAM-1377 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 1.3.0.BETA1 It would be nice if there were a dispatcher for the Spring TaskExecutor abstraction providing dispatchers for Quartz, WorkManager API, etc. http://static.springframework.org/spring/docs/2.0.x/reference/scheduling.... -- 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

18 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1223) Better example usage of @Unwrap

by Pete Muir (JIRA)

Better example usage of @Unwrap ------------------------------- Key: JBSEAM-1223 URL: http://jira.jboss.com/jira/browse/JBSEAM-1223 Project: JBoss Seam Issue Type: Bug Components: Documentation Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Pete Muir Priority: Trivial -- 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

18 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1108) Loosen restrictions around @PersistenceContext

by Michael Youngstrom (JIRA)

Loosen restrictions around @PersistenceContext ---------------------------------------------- Key: JBSEAM-1108 URL: http://jira.jboss.com/jira/browse/JBSEAM-1108 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.0.GA Reporter: Michael Youngstrom Fix For: 1.3.0.BETA1 Spring can utilize the @PersistenceContext annotation in a bean to auto inject an EntityManager. However, if you create a Spring bean with @PersistenceContext on one of its fields and make it a Seam component Seam assumes that's invalid and throws an exception. It would be nice if Seam could loosen validation of the @PersistenceContext to better accommodate unconventional uses. Caused by: java.lang.IllegalArgumentException: @PersistenceContext may only be used on session bean or message driven bean components: userService at org.jboss.seam.Component.initMembers(Component.java:663) at org.jboss.seam.Component.<init>(Component.java:253) at org.jboss.seam.Component.<init>(Component.java:203) at org.jboss.seam.ioc.IoCComponent.<init>(IoCComponent.java:56) at org.jboss.seam.ioc.spring.SpringComponent.<init>(SpringComponent.java:152) at org.jboss.seam.ioc.spring.SpringComponent.addSpringComponent(SpringComponent.java:82) at org.jboss.seam.ioc.spring.SeamNamespaceHandler$SeamComponentBeanDefinitionDecorator.decorate(SeamNamespaceHandler.java:186) at org.springframework.beans.factory.xml.NamespaceHandlerSupport.decorate(NamespaceHandlerSupport.java:106) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.decorateIfRequired(BeanDefinitionParserDelegate.java:1142) at org.springframework.beans.factory.xml.BeanDefinitionParserDelegate.decorateBeanDefinitionIfRequired(BeanDefinitionParserDelegate.java:1132) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.processBeanDefinition(DefaultBeanDefinitionDocumentReader.java:237) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseDefaultElement(DefaultBeanDefinitionDocumentReader.java:151) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:130) at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:90) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:458) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:353) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:303) at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:280) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:131) at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:147) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:124) at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:92) at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:100) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:298) at org.jboss.seam.ioc.spring.ContextLoader.startupContextLoader(ContextLoader.java:59) at org.jboss.seam.ioc.spring.ContextLoader.create(ContextLoader.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.jboss.seam.util.Reflections.invoke(Reflections.java:20) at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:123) at org.jboss.seam.Component.callComponentMethod(Component.java:1834) at org.jboss.seam.Component.callCreateMethod(Component.java:1757) at org.jboss.seam.Component.newInstance(Component.java:1746) at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:175) at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:145) at org.jboss.seam.init.Initialization.init(Initialization.java:504) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) -- 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

18 years, 10 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1076) @Synchronized does not work for any Spring managed Seam components

by Michael Youngstrom (JIRA)

@Synchronized does not work for any Spring managed Seam components ------------------------------------------------------------------ Key: JBSEAM-1076 URL: http://jira.jboss.com/jira/browse/JBSEAM-1076 Project: JBoss Seam Issue Type: Bug Components: Spring Affects Versions: 1.2.0.GA Reporter: Michael Youngstrom Fix For: 1.2.1.GA @Synchronized cannot be used with any spring managed seam components created using <seam:component/>. The reason is if spring is managing the scope of the seam component (singleton, prototype, custom) then the spring integration will make the Component scope STATELESS so that seam will defer to spring everytime it requests an instance of the object. There is a check in the component constructor that @Synchronized cannot be used with STATELESS components. It would be nice if this check could be removed to better support non standard use of the STATELESS scope like the Spring integration and perhaps the microcontainer integration. -- 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

18 years, 10 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1217) Port @Asynchronous Interceptor to Spring

by Michael Youngstrom (JIRA)

Port @Asynchronous Interceptor to Spring ---------------------------------------- Key: JBSEAM-1217 URL: http://jira.jboss.com/jira/browse/JBSEAM-1217 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 1.2.1.GA Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 1.3.0.BETA1 It would be nice to create a port of the @Asynchronous seam interceptor to the Spring TaskExecutor API which will provide asynchronous execution support to Spring using technologies such as the WorkManager API (JSR 237) and @Asynchronous support in a non J2EE container environment. -- 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

18 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-542) Migrate back to seperate microcontainer/lib and embedded-ejb/lib distribution and create an ant/lib dir

by Gavin King (JIRA)

Migrate back to seperate microcontainer/lib and embedded-ejb/lib distribution and create an ant/lib dir ------------------------------------------------------------------------------------------------------- Key: JBSEAM-542 URL: http://jira.jboss.com/jira/browse/JBSEAM-542 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Gavin King Assigned To: Gavin King Fix For: 1.2.0.BETA1 we should consider splitting this stuff back out 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

18 years, 10 months

2
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2007