February 2012 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-4903) NullPointerException in SeamListener

by Fagner Silva (JIRA)

Fagner Silva created JBSEAM-4903: ------------------------------------ Summary: NullPointerException in SeamListener Key: JBSEAM-4903 URL: https://issues.jboss.org/browse/JBSEAM-4903 Project: Seam 2 Issue Type: Bug Components: Framework Affects Versions: 2.2.1.Final Environment: Ubuntu 11.10 Java 7 JBoss AS 7.1.0CR1b Eclipse Indigo Reporter: Fagner Silva Priority: Blocker I'm trying to migrate an application from Seam 2 to JBoss 7. I followed these steps (https://community.jboss.org/blogs/marek-novotny/2011/07/29/seam-2-booking...), but i'm getting this error: 11:27:18,627 Grave [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-4) JSF1051: Service entry 'org.jboss.as.web.deployment.jsf.JsfInjectionProvider' does not extend DiscoverableInjectionProvider. Entry will be ignored. 11:27:18,629 Informações [javax.enterprise.resource.webcontainer.jsf.application] (MSC service thread 1-4) JSF1048: PostConstruct/PreDestroy annotations present. ManagedBeans methods marked with these annotations will have said annotations processed. 11:27:19,187 ERROR [stderr] (MSC service thread 1-4) log4j:WARN No appenders could be found for logger (javax.servlet.ServletContextListener). 11:27:19,187 ERROR [stderr] (MSC service thread 1-4) log4j:WARN Please initialize the log4j system properly. 11:27:19,188 ERROR [stderr] (MSC service thread 1-4) log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 11:27:30,098 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/portalusuario]] (MSC service thread 1-4) Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.NullPointerException at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1170) [jboss-seam-2.2.1.Final.jar:2.2.1.Final] at org.jboss.seam.init.Initialization.init(Initialization.java:737) [jboss-seam-2.2.1.Final.jar:2.2.1.Final] at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam-2.2.1.Final.jar:2.2.1.Final] at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3392) [jbossweb-7.0.7.Final.jar:] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3850) [jbossweb-7.0.7.Final.jar:] at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:77) [jboss-as-web-7.1.0.CR1b.jar:7.1.0.CR1b] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [:1.7.0_01] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.7.0_01] at java.lang.Thread.run(Unknown Source) [:1.7.0_01] 11:27:30,102 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Error listenerStart 11:27:30,103 ERROR [org.apache.catalina.core.StandardContext] (MSC service thread 1-4) Context [/portalusuario] startup failed due to previous errors 11:27:30,109 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.web.deployment.default-host./portalusuario: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./portalusuario: failed to start context at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:82) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:1.0.1.GA] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [:1.7.0_01] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [:1.7.0_01] at java.lang.Thread.run(Unknown Source) [:1.7.0_01] 11:27:30,319 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015856: Undeploy of deployment "portalusuario.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./portalusuario" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./portalusuario: failed to start context"}} 11:27:30,321 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report JBAS014777: Services which failed to start: service jboss.web.deployment.default-host./portalusuario: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./portalusuario: failed to start context 11:27:30,326 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./portalusuario" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./portalusuario: failed to start context"}}}} 11:27:30,365 INFO [org.jboss.jpa] (MSC service thread 1-7) JBAS011403: Stopping Persistence Unit Service 'portalusuario.war#portalusuarioDB' 11:27:30,366 INFO [org.hibernate.impl.SessionFactoryImpl] (MSC service thread 1-7) closing 11:27:30,454 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment portalusuario.war in 133ms Since I hadn't found any hint to that kind of error I'm reporting here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

2
6
0 / 0

[JBoss JIRA] Created: (SEAMFACES-200) Add detail text for FacesMessage in MessageAdapter

by Sebastian Sachtleben (JIRA)

Add detail text for FacesMessage in MessageAdapter -------------------------------------------------- Key: SEAMFACES-200 URL: https://issues.jboss.org/browse/SEAMFACES-200 Project: Seam Faces Issue Type: Feature Request Components: Messages & i18n Reporter: Sebastian Sachtleben Priority: Minor We have added detail text implementation for i18n messages in Seam International Module (see SEAMINTL-55). After next tag iteration (CR1) we could add this detail text to the FacesMessage in MessageAdapter like: new FacesMessage(severity, summary, detail); I could take it just assign it to me. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAM-71) Seam-booking example: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed'

by Marek Schmidt (JIRA)

Seam-booking example: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed' -------------------------------------------------------------------------------------------------------------------------------------------------- Key: SEAM-71 URL: https://issues.jboss.org/browse/SEAM-71 Project: Seam 3 Distribution Issue Type: Bug Components: Shared Examples Affects Versions: 3.0.0.Final Environment: JBossAS6 Reporter: Marek Schmidt Priority: Minor Fix For: Future In seam-booking example, there is a navigation case missing for the "failed" outcome in the login action, which causes an ugly message to be displayed when entering wrong credentials: Unable to find matching navigation case with from-view-id '/home.xhtml' for action '#{identity.login}' with outcome 'failed' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] (SEAMREPORTS-34) Upgrade XDocReports to 0.9.6

by George Gastaldi (JIRA)

George Gastaldi created SEAMREPORTS-34: ------------------------------------------ Summary: Upgrade XDocReports to 0.9.6 Key: SEAMREPORTS-34 URL: https://issues.jboss.org/browse/SEAMREPORTS-34 Project: Seam Reports Issue Type: Library Upgrade Reporter: George Gastaldi -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
5
0 / 0

[JBoss JIRA] (JBSEAM-4897) jboss-seam-jul Log4JConversionFilter is incompatable with jboss-logmanager

by Brent Douglas (JIRA)

Brent Douglas created JBSEAM-4897: ------------------------------------- Summary: jboss-seam-jul Log4JConversionFilter is incompatable with jboss-logmanager Key: JBSEAM-4897 URL: https://issues.jboss.org/browse/JBSEAM-4897 Project: Seam 2 Issue Type: Bug Components: Core Affects Versions: 2.2.2.Final Environment: AS7 7.1.0.Final-SNAPSHOT, seam-2.2.2.Final Reporter: Brent Douglas logmanager.Logger expects Log4JConversionFilter.isLoggable(LogRecord) to return if the record is loggable while Log4JConversionFilter delegates back to the logger instead resulting in a stack overflow. I don't know if AS7 is supported with seam2 but this is the first actual problem I've come across while running on it. {code} Caused by: java.lang.StackOverflowError at java.util.logging.LogRecord.getMessage(LogRecord.java:320) [:1.6.0_30] at java.util.logging.Formatter.formatMessage(Formatter.java:97) [:1.6.0_30] at org.jboss.seam.interop.jul.Log4JConversionFilter.logWithThrowable(Log4JConversionFilter.java:81) [jboss-seam-jul-2.2.2.Final.jar:2.2.2.Final] at org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:68) [jboss-seam-jul-2.2.2.Final.jar:2.2.2.Final] at org.jboss.logmanager.Logger.logRaw(Logger.java:640) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.log4j.BridgeLogger.error(BridgeLogger.java:72) at org.jboss.seam.interop.jul.Log4JConversionFilter.logWithThrowable(Log4JConversionFilter.java:86) [jboss-seam-jul-2.2.2.Final.jar:2.2.2.Final] at org.jboss.seam.interop.jul.Log4JConversionFilter.isLoggable(Log4JConversionFilter.java:68) [jboss-seam-jul-2.2.2.Final.jar:2.2.2.Final] at org.jboss.logmanager.Logger.logRaw(Logger.java:640) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.Logger.log(Logger.java:600) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.Logger.log(Logger.java:612) [jboss-logmanager-1.2.0.GA.jar:1.2.0.GA] at org.jboss.logmanager.log4j.BridgeLogger.error(BridgeLogger.java:72) ... {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
3
0 / 0

[JBoss JIRA] (SEAMFACES-241) SecurityPhaseListener#observePreNavigateEvent not firing PostLoginEvent when view action is #{identity.login()}

by Fernando Marquardt (JIRA)

Fernando Marquardt created SEAMFACES-241: -------------------------------------------- Summary: SecurityPhaseListener#observePreNavigateEvent not firing PostLoginEvent when view action is #{identity.login()} Key: SEAMFACES-241 URL: https://issues.jboss.org/browse/SEAMFACES-241 Project: Seam Faces Issue Type: Bug Components: Security Affects Versions: 3.1.0.Final Environment: Seam Faces 3.1.0.Final Seam Security 3.1.0.Final JavaEE6 Jboss 7.0.2 Reporter: Fernando Marquardt I'm trying to use the "redirect to captured view after login succesful" feature implemented by Seam Faces. org.jboss.seam.faces.security.SecurityPhaseListener#observePreNavigateEvent should fire a PostLoginEvent if the authentication response was 'success' (Identity.RESPONSE_LOGIN_SUCCESS) and if the event action is equals to '#{identity.login}'. My problem is when my action on the commandButton is '#{identity.login()}', wich is suggested by my IDE (Eclipse), wich i think is perfectly fine. So the verification '"#{identity.login}".equals(event.getFromAction())' returns false and the PostLoginEvent is never fired. This is necessary for the org.jboss.seam.faces.security.LoginListener#observePostLoginEvent to be invoked to do the redirection. I can use a workaround, by rewriting my action to '#{identity.login}' and it will work fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
2
0 / 0

[JBoss JIRA] (SEAMREPORTS-33) Upgrade XDocReports to 0.9; 4

by George Gastaldi (JIRA)

George Gastaldi created SEAMREPORTS-33: ------------------------------------------ Summary: Upgrade XDocReports to 0.9;4 Key: SEAMREPORTS-33 URL: https://issues.jboss.org/browse/SEAMREPORTS-33 Project: Seam Reports Issue Type: Library Upgrade Reporter: George Gastaldi Fix For: The Future -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
7
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-26) Make caught exception available as named bean

by Dan Allen (JIRA)

Make caught exception available as named bean --------------------------------------------- Key: SEAMCATCH-26 URL: https://issues.jboss.org/browse/SEAMCATCH-26 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Reporter: Dan Allen Assignee: Jason Porter Priority: Minor As we get into error pages, it's going to be useful to have the caught exception available via a named bean. I think this is just a matter of adding a dependent-scoped producer that reads the value of the current CaughtException from a field in the exception dispatcher. In Seam 2, the following two variables were available: org.jboss.seam.caughtException - the original exception that was caught org.jboss.seam.handledException - the exception cause currently being handled I think we could just map org.jboss.seam.caughtException to CaughtException...that way all the info is available, including the exception being handled, the original exception and the unwrapped stack. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
12
0 / 0

[JBoss JIRA] (SEAMFACES-238) Theme handling for Seam 3

by Dupont Dupont (JIRA)

Dupont Dupont created SEAMFACES-238: --------------------------------------- Summary: Theme handling for Seam 3 Key: SEAMFACES-238 URL: https://issues.jboss.org/browse/SEAMFACES-238 Project: Seam Faces Issue Type: Feature Request Reporter: Dupont Dupont Bring theme handling functionnality from Seam 2 into CDI. See http://docs.jboss.org/seam/2.2.2.Final/reference/en-US/html/i18n.html#d0e... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (SEAMFACES-168) Error page navigation after Seam Catch

by Andrew Wheeler (JIRA)

Error page navigation after Seam Catch -------------------------------------- Key: SEAMFACES-168 URL: https://issues.jboss.org/browse/SEAMFACES-168 Project: Seam Faces Issue Type: Feature Request Components: Conversations Affects Versions: 3.0.1 Environment: JBoss AS6, Mojarra 2.1 Reporter: Andrew Wheeler It would be nice to annotate a Seam Catch handler with an error page view that is restored after the exception has been handled. This should tidy (destroy) any active conversation as the view probably can't be restored. It could also mark the event as handled (some default behaviour) if it hasn't been handled by the exception handler method. E.g: @ErrorPage("error") public void noConversationHandler(@Handles CaughtException<NonexistentConversationException> event) { messages.info("The view you were editing has expired."); } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 10 months

3
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2012