April 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMXML-21) Field references should support value attribute

by Dan Allen (JIRA)

Field references should support value attribute ----------------------------------------------- Key: SEAMXML-21 URL: https://jira.jboss.org/browse/SEAMXML-21 Project: Seam XML Configuration Issue Type: Feature Request Affects Versions: 3.0.0.Alpha3 Reporter: Dan Allen Field references should support a value attribute if the field type is a convertable type* (Seam XML knows how to turn it into an object). This will drastically simplify the appearance and verbosity of a field definitions, particularly virtual fields. Consider the configuration of the default locale as an example. Presently, it would be configured as follows: <String> <Produces/> <lc:DefaultLocale/> <value>fr</value> </String> Since String is a convertable type, the proposed change would allow it to be simplified to: <String value="fr"> <Produces/> <lc:DefaultLocale/> </String> Another example would be assigning an numeric value to a bean field. Presently, the configuration is: <x:Account> <x:balance> <value>100</value> </x:balance> </x:Account> With support for the value attribute, this could be simplified to: <x:Account> <x:balance value="100"/> </x:Account> If the type being configured has a value property, then of course the value attribute would assign the value of property named "value" instead of being treated as the overall value of the field. * Examples of convertable types are string, date, number, etc. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMXML-2) match XML namespace to package and subpackages (or multiple packages)

by Dan Allen (JIRA)

match XML namespace to package and subpackages (or multiple packages) --------------------------------------------------------------------- Key: SEAMXML-2 URL: https://jira.jboss.org/jira/browse/SEAMXML-2 Project: Seam XML Issue Type: Feature Request Reporter: Dan Allen Assignee: Pete Muir To avoid an explosion of namespace declarations (which increases complexity and reduces readability), there should be a way to have a urn:java namespace URL match not only one Java package, but multiple packages. Perhaps, a namespace will match a package and any sub-packages. Multiple package mapping is done internally to the url:java:seam:core namespace. The user needs a way to do the same. Otherwise, modules will need to use a flat directory structure to avoid burdening the end developer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
8
0 / 0

[JBoss JIRA] Created: (SEAMXML-17) If a user adds a scope to an type it should override an existing scope

by Stuart Douglas (JIRA)

If a user adds a scope to an type it should override an existing scope ---------------------------------------------------------------------- Key: SEAMXML-17 URL: https://jira.jboss.org/browse/SEAMXML-17 Project: Seam XML Bean Config Issue Type: Feature Request Affects Versions: 3.0.0.Alpha2 Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-14) Support setting fields using EL

by Stuart Douglas (JIRA)

Support setting fields using EL ------------------------------- Key: SEAMXML-14 URL: https://jira.jboss.org/browse/SEAMXML-14 Project: Seam XML Bean Config Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-12) Support complex initial values

by Jozef Hartinger (JIRA)

Support complex initial values ------------------------------ Key: SEAMXML-12 URL: https://jira.jboss.org/browse/SEAMXML-12 Project: Seam XML Bean Config Issue Type: Feature Request Affects Versions: 3.0.0.Alpha2 Reporter: Jozef Hartinger Assignee: Stuart Douglas Currently, setting the value of a field is limited to the following basic types: {primitives, Date, Calendar, Enum, Class}. This is not enough for complex cases. It would be great if any class instance could be configured via XML extension and injected into a field. Here is an example public class Car { private String color; // getters and setters } @ApplicationScoped public class Garage { private Set<Car> cars // getters and setters } The garage bean could be configured the following way: <p:Garage> <s:overrides /> <p:cars> <s:value> <p:Car color="blue" /> </s:value> <s:value> <p:Car color="red" /> </s:value> </p:cars> </p:Garage> or maybe even: <p:Garage> <s:overrides /> <p:cars> <p:Car color="blue" /> <p:Car color="red" /> </p:cars> </p:Garage> I can see the execution steps as: 1) Check that Car is a dependent-scoped component 2) For each element inside p:cars a) obtain a (dependent) Car instance from BeanManager b) set properties of the Car instance c) garage.add(car) This is a different approach to configuration compared what the XML extension provides so far. While it is currently possible to configure beans, if this feature request is implemented, it will be possible to configure bean instances separately and use these instances to configure a bean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (SEAMXML-29) Unable to run princess-rescue example with embedded tomcat

by Martin Gencur (JIRA)

Unable to run princess-rescue example with embedded tomcat ---------------------------------------------------------- Key: SEAMXML-29 URL: https://issues.jboss.org/browse/SEAMXML-29 Project: Seam Config Issue Type: Bug Affects Versions: 3.0.0.Beta2 Reporter: Martin Gencur Fix For: 3.0.0.CR1 The example works fine with both JBossAS 6 Final and embedded Jetty. It cannot deploy to Tomcat, though. I'm getting the following exception when running "mvn tomcat:run" from within the example. Jan 31, 2011 1:21:01 PM com.sun.faces.config.ConfigureListener contextInitialized INFO: Initializing Mojarra 2.0.2 (FCS b10) for context '/princess-rescue' Jan 31, 2011 1:21:02 PM com.sun.faces.config.ConfigManager initialize INFO: Unsanitized stacktrace from failed start... com.sun.faces.config.ConfigurationException: Source Document: jar:file:/home/mgencur/.m2/repository/org/jboss/weld/servlet/weld-servlet/1.1.0.CR2/weld-servlet-1.1.0.CR2.jar!/META-INF/faces-config.xml Cause: Unable to create a new instance of 'org.jboss.weld.jsf.ConversationAwareViewHandler': java.lang.reflect.InvocationTargetException at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:295) at com.sun.faces.config.processor.ApplicationConfigProcessor.setViewHandler(ApplicationConfigProcessor.java:527) at com.sun.faces.config.processor.ApplicationConfigProcessor.processViewHandlers(ApplicationConfigProcessor.java:847) at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:331) at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:223) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:335) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:223) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.startup.Embedded.start(Embedded.java:825) at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:385) at org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:144) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:265) ... 39 more Caused by: java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:58) at org.jboss.weld.jsf.ConversationAwareViewHandler.<init>(ConversationAwareViewHandler.java:71) ... 44 more Jan 31, 2011 1:21:02 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Exception sending context initialized event to listener instance of class com.sun.faces.config.ConfigureListener com.sun.faces.config.ConfigurationException: CONFIGURATION FAILED! Singleton is not set at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:354) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:223) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.startup.Embedded.start(Embedded.java:825) at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:385) at org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:144) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:153) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:451) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:188) at org.apache.maven.cli.MavenCli.main(MavenCli.java:134) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.IllegalStateException: Singleton is not set at org.jboss.weld.bootstrap.api.helpers.IsolatedStaticSingletonProvider$IsolatedStaticSingleton.get(IsolatedStaticSingletonProvider.java:52) at org.jboss.weld.Container.instance(Container.java:58) at org.jboss.weld.jsf.ConversationAwareViewHandler.<init>(ConversationAwareViewHandler.java:71) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.sun.faces.config.processor.AbstractConfigProcessor.createInstance(AbstractConfigProcessor.java:265) at com.sun.faces.config.processor.ApplicationConfigProcessor.setViewHandler(ApplicationConfigProcessor.java:527) at com.sun.faces.config.processor.ApplicationConfigProcessor.processViewHandlers(ApplicationConfigProcessor.java:847) at com.sun.faces.config.processor.ApplicationConfigProcessor.process(ApplicationConfigProcessor.java:331) at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) at com.sun.faces.config.processor.LifecycleConfigProcessor.process(LifecycleConfigProcessor.java:116) at com.sun.faces.config.processor.AbstractConfigProcessor.invokeNext(AbstractConfigProcessor.java:114) at com.sun.faces.config.processor.FactoryConfigProcessor.process(FactoryConfigProcessor.java:223) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:335) ... 31 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (SEAMXML-44) Detect config in WEB-INF that cannot be read and log a warning

by Stuart Douglas (JIRA)

Detect config in WEB-INF that cannot be read and log a warning -------------------------------------------------------------- Key: SEAMXML-44 URL: https://issues.jboss.org/browse/SEAMXML-44 Project: Seam Config Issue Type: Feature Request Reporter: Stuart Douglas -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] Created: (SEAMXML-37) reference document translation(chinese)

by kuu yee (JIRA)

reference document translation(chinese) --------------------------------------- Key: SEAMXML-37 URL: https://issues.jboss.org/browse/SEAMXML-37 Project: Seam Config Issue Type: Feature Request Components: Documentation Affects Versions: 3.0.0.CR1 Reporter: kuu yee Fix For: 3.0.0.Final -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMXML-15) Allow configuration of virtual producer fields via XML

by Stuart Douglas (JIRA)

Allow configuration of virtual producer fields via XML ------------------------------------------------------ Key: SEAMXML-15 URL: https://jira.jboss.org/browse/SEAMXML-15 Project: Seam XML Bean Config Issue Type: Feature Request Reporter: Stuart Douglas Assignee: Stuart Douglas seam-xml should support configuring 'virtual' producer fields, e.g. <s:EntityManager> <s:Produces/> <s:PersistenceContext/> <my:SomeQualifier/> </s:EntityManager> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMXML-41) The princess-rescue example does not follow the Seam example naming convention

by Jozef Hartinger (JIRA)

The princess-rescue example does not follow the Seam example naming convention ------------------------------------------------------------------------------ Key: SEAMXML-41 URL: https://issues.jboss.org/browse/SEAMXML-41 Project: Seam Config Issue Type: Bug Components: Build Infrastructure Affects Versions: 3.0.0.CR4 Reporter: Jozef Hartinger Fix For: 3.0.0.Final The following naming convention is enforced: * folder name in the seam distribution - <module name>-<example name> (e.g. rest-tasks) * example final name (context path after deployment) - should be the same as above (e.g. rest-tasks) * maven artifactId - seam-<module name>\-example\-<example name> (e.g. seam-rest-example-tasks) The princess-rescue example should declare "config-princess-rescue" as its final name. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011