March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1127) Allow inspection of all installed components

by Mike Quilleash (JIRA)

Allow inspection of all installed components -------------------------------------------- Key: JBSEAM-1127 URL: http://jira.jboss.com/jira/browse/JBSEAM-1127 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash Add a method, probably to Component, to allow the installed components to be queried. Could either scan the application context for "*.component" or just build a list during initialisation and return it. public List< Component > getInstalledComponents() { // TODO: } -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1022) Resin support for JBoss Seam

by Siarhei Dudzin (JIRA)

Resin support for JBoss Seam ---------------------------- Key: JBSEAM-1022 URL: http://jira.jboss.com/jira/browse/JBSEAM-1022 Project: JBoss Seam Issue Type: Feature Request Reporter: Siarhei Dudzin Fix For: 1.2.0.GA Support for Resin -- 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, 11 months

4
17
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1002) Have injection check for existing component

by Chuck Adams (JIRA)

Have injection check for existing component ------------------------------------------- Key: JBSEAM-1002 URL: http://jira.jboss.com/jira/browse/JBSEAM-1002 Project: JBoss Seam Issue Type: Feature Request Reporter: Chuck Adams Right now, if a component is injected from an unbound context variable, it is treated as if it were null. Consequently if a field/setter is misspelled or not renamed when a component is renamed, this results in errors at the time the component is injected or accessed. When components are first set up, there should be a warning logged if there are any injections detected for context variables that were never defined or outjected anywhere. -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-949) Support Other Context Stores (not just session and jBPM)

by Adam Brod (JIRA)

Support Other Context Stores (not just session and jBPM) -------------------------------------------------------- Key: JBSEAM-949 URL: http://jira.jboss.com/jira/browse/JBSEAM-949 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Reporter: Adam Brod Seam should support persisting the Conversation scope in other stores other than Http Session and jBPM. For example, since our Conversations can get very large, we want to store our conversations in a non-replicated Tangosol cache - separate from Http Session. I can imagine that other people may want to store conversations in other stores such Filesystem, DB, home-grown cache, etc. -- 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, 11 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-923) filter creation failure

by jarkko Lietolahti (JIRA)

filter creation failure ----------------------- Key: JBSEAM-923 URL: http://jira.jboss.com/jira/browse/JBSEAM-923 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.7.CR1 Reporter: jarkko Lietolahti in components.xml: <core:filter name="customerFilter"> <core:name>customer</core:name> <core:parameters> <key>id</key> <value>1</value> </core:parameters> </core:filter> <core:managed-persistence-context name="tc3EntityManager" persistence-unit-jndi-name="java:/tc3ManagerFactory" auto-create="true"> <core:filters> <value>#{customerFilter}</value> </core:filters> </core:managed-persistence-context> causes this when deploying: 23:15:13,437 INFO [Component] Component: customerFilter, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Filter 23:15:13,441 ERROR [[/TrueConcept]] Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener java.lang.RuntimeException: Could not create Component: customerFilter at org.jboss.seam.init.Initialization.addComponent(Initialization.java:806) at org.jboss.seam.init.Initialization.addComponents(Initialization.java:693) at org.jboss.seam.init.Initialization.init(Initialization.java:454) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) 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.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) 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.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) Caused by: java.lang.IllegalArgumentException: No converter for type: org.jboss.seam.core.Expressions$ValueBinding at org.jboss.seam.util.Conversions.getConverter(Conversions.java:55) at org.jboss.seam.Component$ConstantInitialValue.<init>(Component.java:1998) at org.jboss.seam.Component.getInitialValue(Component.java:421) at org.jboss.seam.Component.access$200(Component.java:135) at org.jboss.seam.Component$MapInitialValue.<init>(Component.java:2150) at org.jboss.seam.Component.getInitialValue(Component.java:417) at org.jboss.seam.Component.getTopInitialValue(Component.java:401) at org.jboss.seam.Component.initInitializers(Component.java:379) at org.jboss.seam.Component.<init>(Component.java:264) at org.jboss.seam.Component.<init>(Component.java:205) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:796) at org.jboss.seam.init.Initialization.addComponents(Initialization.java:693) at org.jboss.seam.init.Initialization.init(Initialization.java:454) at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3763) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4211) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) 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.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 23:15:13,442 ERROR [StandardContext] Error listenerStart -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-853) Add some additional functionality for programmatically manipulating pages

by Mike Quilleash (JIRA)

Add some additional functionality for programmatically manipulating pages ------------------------------------------------------------------------- Key: JBSEAM-853 URL: http://jira.jboss.com/jira/browse/JBSEAM-853 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Environment: Any Reporter: Mike Quilleash It would be useful (for me at least) to be able to override a definition in pages.xml. I would suggest the following.. newPage - create a blank page, replacing any existing page removePage - remove a page entry getPage - change semantic to return null if a page doesn't exist rather than creating a new page (alternative hasPage for determining if a page is present) Allow newPage/removePage/getPage to create/remove/access wildcarded pages. Main tricky thing is the pageStack cache which could just be removed as it didn't look as though the stack building was that expensive. Otherwise it would need to be invalidated on modifications to the pages map. -- 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, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-786) Quick reference guide/cheat sheet for core

by Peter Muir (JIRA)

Quick reference guide/cheat sheet for core ------------------------------------------ Key: JBSEAM-786 URL: http://jira.jboss.com/jira/browse/JBSEAM-786 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.1.5.GA Reporter: Peter Muir Priority: Optional The reference guide is a great resource, but the documentation for core is now probably about 100 pages long (so leaving out mail, text, security, pdf, tools, tutorials I guess). Further the documentation for something like pages.xml is split over at least three chapters (conversation flow, security, events). Some sort of cheat sheet would be handy for more experienced bods that really just listed out the annotations (with attributes), components, JSF tags, elements for pages.xml and components.xml would be cool. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-782) Email aware workflow example

by Peter Muir (JIRA)

Email aware workflow example ---------------------------- Key: JBSEAM-782 URL: http://jira.jboss.com/jira/browse/JBSEAM-782 Project: JBoss Seam Issue Type: Feature Request Components: BPM, Mail Affects Versions: 1.1.5.GA Reporter: Peter Muir Assigned To: Peter Muir An example to demonstrate both jboss-seam-mail and mail-ra (aka sending and receiving) integrated with jbpm (users can progress through tasks using email) -- 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, 11 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-772) Use @EJB to invoke remote ejb in pojo

by Kuisong Tong (JIRA)

Use @EJB to invoke remote ejb in pojo ------------------------------------- Key: JBSEAM-772 URL: http://jira.jboss.com/jira/browse/JBSEAM-772 Project: JBoss Seam Issue Type: Feature Request Reporter: Kuisong Tong Fix For: 1.1.6.GA -- 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, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-722) Add a component generator component that allows one to sub-type Component

by Bill Wallace (JIRA)

Add a component generator component that allows one to sub-type Component ------------------------------------------------------------------------- Key: JBSEAM-722 URL: http://jira.jboss.com/jira/browse/JBSEAM-722 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.1.GA Reporter: Bill Wallace It would be very nice to be able to specify what Component class is to be used within a package, so that one can, for instance, over-ride or extend the initialization code. Adding such over-riding would allow one to efficiently write annotations such as: @Property("#{property-setter-for-initialization-time}) instead of @In which would provide initialization time object injection. I know you can do this by specifying properties in the components.xml file, or seam.properties file, but it is rather a pain to have to create an xml file just to specify an extra property of that type. I know you can do this with @In, but that executes per-method call, and I'd like to see a version that only executes on instantiation. Of course, one can create an initializer class that gets called from an @Create that performs this same data, but I'd like to be able to store the rest of the meta-data at the class level and view it in the debug page automatically, the same as the rest of the properties. I also have some more complex applications for reading in initialization data. -- 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, 11 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues March 2007