April 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMJCR-17) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMJCR-17 URL: https://issues.jboss.org/browse/SEAMJCR-17 Project: Seam JCR Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMJMS-27) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMJMS-27 URL: https://issues.jboss.org/browse/SEAMJMS-27 Project: Seam JMS Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (SEAMREMOTING-36) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMREMOTING-36 URL: https://issues.jboss.org/browse/SEAMREMOTING-36 Project: Seam Remoting Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-60) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMSECURITY-60 URL: https://issues.jboss.org/browse/SEAMSECURITY-60 Project: Seam Security Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SOLDER-101) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SOLDER-101 URL: https://issues.jboss.org/browse/SOLDER-101 Project: Seam Solder Issue Type: Task Reporter: Jason Porter There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-56) OpenID RP login doesn't reset authentication state on failure

by Patrick McFarland (JIRA)

OpenID RP login doesn't reset authentication state on failure ------------------------------------------------------------- Key: SEAMSECURITY-56 URL: https://issues.jboss.org/browse/SEAMSECURITY-56 Project: Seam Security Issue Type: Bug Reporter: Patrick McFarland Currently, the OpenID RP example doesn't reset the authentication state on failure to authenticate. Go to the login form, select MyOpenID, hit login, hit cancel while on the MyOpenID site, you will be redirected to the AuthenticationFailed.xhtml; from there, go back to the login form and try logging in. This will produce an exception that is logged only (you are redirected back to the login form, which now works): ERROR [org.jboss.seam.security.IdentityImpl] Login failed: java.lang.IllegalStateException: Authentication already in progress. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-148) Certain bean scopes prevent application to start on tomcat (either 6 or 7)

by brvno brvnic (JIRA)

Certain bean scopes prevent application to start on tomcat (either 6 or 7) -------------------------------------------------------------------------- Key: SEAMFACES-148 URL: https://issues.jboss.org/browse/SEAMFACES-148 Project: Seam Faces Issue Type: Bug Components: CDI Integration Affects Versions: 3.0.0.Final Environment: tomcat 6 or 7 Reporter: brvno brvnic When deploying the simplest application with cdi+seamfaces to Tomcat 6 or 7 certain scopes prevents application to start succesfully. Scopes that work are @RequestScoped and @ApplicationScoped, however other scopes (@SessionScoped,@ViewScoped,@RenderScoped,@ConversationScoped) break the application with the following exception: org.jboss.seam.solder.beanManager.BeanManagerUnavailableException: Failed to locate BeanManager using any of these providers: org.jboss.seam.solder.beanManager.DefaultJndiBeanManagerProvider(11), org.jboss.seam.solder.beanManager.ServletContainerJndiBeanManagerProvider(10) at org.jboss.seam.solder.beanManager.BeanManagerLocator.getBeanManager(BeanManagerLocator.java:91) at org.jboss.seam.solder.beanManager.BeanManagerAware.getBeanManager(BeanManagerAware.java:56) at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:25) at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:43) at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:34) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2040) at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2016) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:298) at org.jboss.weld.environment.servlet.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:330) at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:598) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Apr 20, 2011 10:04:24 AM 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! Failed to locate BeanManager using any of these providers: org.jboss.seam.solder.beanManager.DefaultJndiBeanManagerProvider(11), org.jboss.seam.solder.beanManager.ServletContainerJndiBeanManagerProvider(10) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:351) at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:220) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4205) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4704) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Caused by: org.jboss.seam.solder.beanManager.BeanManagerUnavailableException: Failed to locate BeanManager using any of these providers: org.jboss.seam.solder.beanManager.DefaultJndiBeanManagerProvider(11), org.jboss.seam.solder.beanManager.ServletContainerJndiBeanManagerProvider(10) at org.jboss.seam.solder.beanManager.BeanManagerLocator.getBeanManager(BeanManagerLocator.java:91) at org.jboss.seam.solder.beanManager.BeanManagerAware.getBeanManager(BeanManagerAware.java:56) at org.jboss.seam.faces.event.AbstractListener.getListeners(AbstractListener.java:25) at org.jboss.seam.faces.event.DelegatingSystemEventListener.getEventListeners(DelegatingSystemEventListener.java:43) at org.jboss.seam.faces.event.DelegatingSystemEventListener.processEvent(DelegatingSystemEventListener.java:34) at javax.faces.event.SystemEvent.processListener(SystemEvent.java:102) at com.sun.faces.application.ApplicationImpl.processListeners(ApplicationImpl.java:2040) at com.sun.faces.application.ApplicationImpl.invokeListenersFor(ApplicationImpl.java:2016) at com.sun.faces.application.ApplicationImpl.publishEvent(ApplicationImpl.java:298) at org.jboss.weld.environment.servlet.jsf.ForwardingApplication.publishEvent(ForwardingApplication.java:330) at com.sun.faces.config.ConfigManager.publishPostConfigEvent(ConfigManager.java:598) at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:341) ... 16 more Apr 20, 2011 10:04:24 AM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Apr 20, 2011 10:04:24 AM org.apache.catalina.core.StandardContext start SEVERE: Context [/facesexample] startup failed due to previous errors Apr 20, 2011 10:04:24 AM com.sun.faces.config.ConfigureListener contextDestroyed SEVERE: Unexpected exception when attempting to tear down the Mojarra runtime java.lang.IllegalStateException: Application was not properly initialized at startup, could not find Factory: javax.faces.application.ApplicationFactory at javax.faces.FactoryFinder$FactoryManager.getFactory(FactoryFinder.java:800) at javax.faces.FactoryFinder.getFactory(FactoryFinder.java:302) at com.sun.faces.config.InitFacesContext.getApplication(InitFacesContext.java:104) at com.sun.faces.config.ConfigureListener.contextDestroyed(ConfigureListener.java:312) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4244) at org.apache.catalina.core.StandardContext.stop(StandardContext.java:4879) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4749) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:840) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:463) at org.apache.catalina.core.StandardService.start(StandardService.java:525) at org.apache.catalina.core.StandardServer.start(StandardServer.java:754) at org.apache.catalina.startup.Catalina.start(Catalina.java:595) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414) Simplest way to reproduce it is to take the weld archetype for servlet: mvn archetype:generate -DarchetypeArtifactId=jboss-jsf-weld-servlet-webapp -DarchetypeGroupId=org.jboss.weld.archetypes -DarchetypeVersion=1.0.1.Beta1 -DarchetypeRepository=central And add dependancies for seam-solder and seamfaces module on the classpath. Than depending on the scope of the HelloWorldBean bean (that is included as a part of the application) the application will start or not. By default the HelloWorldBean is annotated as @Model. Because of that the application manages to start. But if you cnahe its annotations to @Named@SessionScoped for example, the applicaiton will fail on startup. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMVALIDATE-19) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMVALIDATE-19 URL: https://issues.jboss.org/browse/SEAMVALIDATE-19 Project: Seam Validation Issue Type: Task Reporter: Jason Porter Assignee: Gunnar Morling There are some classes (or perhaps all classes) which need to be updated to the new code formatting guidelines, please see https://github.com/seam/build/blob/master/formatting.README for more information -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (SEAMVALIDATE-13) Apply new formatting guidelines

by Gunnar Morling (JIRA)

Apply new formatting guidelines ------------------------------- Key: SEAMVALIDATE-13 URL: https://issues.jboss.org/browse/SEAMVALIDATE-13 Project: Seam Validation Issue Type: Enhancement Reporter: Gunnar Morling Assignee: Gunnar Morling The new formatting guidelines (see http://seamframework.org/Seam3/DevelopmentGuidelines) should be applied to Seam Validation. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4313) EntityHome created/updated/deleted default messages should come from resource bundle instead of hard-coded messages

by Julien Kronegg (JIRA)

EntityHome created/updated/deleted default messages should come from resource bundle instead of hard-coded messages ------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4313 URL: https://jira.jboss.org/jira/browse/JBSEAM-4313 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.2.GA Reporter: Julien Kronegg Priority: Minor The EntityHome default messages on creation/update/deletion are hard-coded in the org.jboss.seam.framework.Home class: protected void initDefaultMessages() { Expressions expressions = new Expressions(); if (createdMessage == null) { createdMessage = expressions.createValueExpression("Successfully created"); } if (updatedMessage == null) { updatedMessage = expressions.createValueExpression("Successfully updated"); } if (deletedMessage == null) { deletedMessage = expressions.createValueExpression("Successfully deleted"); } } While the messages can be updated in the "messages_en.properties" (using "MyEntityClass_created" key for example), this must be done for each entity class. This is painful! It would be nice if we get the following messages decreasing priority for the entity class MyEntityClass: 1. "MyEntityClass_created" 2. "org.jboss.seam.framework.Home_defaultCreated" 3. static message "Successfully created" Note: the example above is given for the creation message only -- 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, 7 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 April 2011