April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1233) Extend @Scope to work on member variables/properties

by Andrew (JIRA)

Extend @Scope to work on member variables/properties ---------------------------------------------------- Key: JBSEAM-1233 URL: http://jira.jboss.com/jira/browse/JBSEAM-1233 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.6.GA Reporter: Andrew I have a relate bug: http://jira.jboss.com/jira/browse/JBSEAM-903 My purpose for this bug was mostly due to binding issues. There are times that I want to have the scope of a member variable to be different from the scope of the bean. Especially, if the bean is conversational and I want the field/property to have event scope. Instead of the proposed @InOut from the above bug, perhaps just extending @Scope would work: @Scope(ScopeType.EVENT) private MyVar myVar; Unlike @In and @Out, this scope would not put use the contexts to get and set values, but simply control the lifecycle of the variable. In this example, myVar could be set to null when the the variables of the bean are out-jected. As it stands, there is no other easy way that I know of to have a variable set to null at then end of a page request. -- 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, 3 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1185) For a validator @Foo(foo="bar", message="#{messages['foo.bar']}") the message bundle should be aware of a parameter called foo

by Pete Muir (JIRA)

For a validator @Foo(foo="bar", message="#{messages['foo.bar']}") the message bundle should be aware of a parameter called foo ------------------------------------------------------------------------------------------------------------------------------ Key: JBSEAM-1185 URL: http://jira.jboss.com/jira/browse/JBSEAM-1185 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Reporter: Pete Muir So then your message can be foo.bar=The value must contain {foo} or sth -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1170) Improve mailbox creation for takeaway example

by Pete Muir (JIRA)

Improve mailbox creation for takeaway example --------------------------------------------- Key: JBSEAM-1170 URL: http://jira.jboss.com/jira/browse/JBSEAM-1170 Project: JBoss Seam Issue Type: Bug Components: Mail Reporter: Pete Muir Assigned To: Pete Muir -- 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, 3 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1175) Seam should issue a warning if both a databinding annotation and @Out occur on the same property

by Pete Muir (JIRA)

Seam should issue a warning if both a databinding annotation and @Out occur on the same property ------------------------------------------------------------------------------------------------ Key: JBSEAM-1175 URL: http://jira.jboss.com/jira/browse/JBSEAM-1175 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Reporter: Pete Muir Priority: Minor -- 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, 3 months

3
7
0 / 0

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

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2007