April 2011 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4216) Seam Component with EJB Timer

by Israel Fonseca (JIRA)

Seam Component with EJB Timer ----------------------------- Key: JBSEAM-4216 URL: https://jira.jboss.org/jira/browse/JBSEAM-4216 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.1.GA Environment: Ubuntu 8.10 x64, JBoss-AS 4.2.3.GA Reporter: Israel Fonseca If a Seam component that triggers a timmer is used, an exception may be throw in the JBoss starting: 13:55:53,646 ERROR [TimerImpl] Error invoking ejbTimeout: java.lang.RuntimeException: java.lang.IllegalStateException: Attempted to invoke a Seam component outside an initialized application And it does make sense, since the timer service tries to execute a method of a seam component before the seam application is started. To solve this i think that EJBs that are seam components should only be started after all the aplications in the server get started, or something like this. I tested it using a timer that generates a log (@Logger) at every minute, and restarting the server (the delayed timmer would be triggered before the Seam App is up). -- 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

3
2
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-39) Simple example produces NullPointerException in server logs when entering wrong user/password

by Marek Schmidt (JIRA)

Simple example produces NullPointerException in server logs when entering wrong user/password --------------------------------------------------------------------------------------------- Key: SEAMSECURITY-39 URL: https://issues.jboss.org/browse/SEAMSECURITY-39 Project: Seam Security Issue Type: Bug Affects Versions: 3.0.0.Beta2 Environment: JBoss AS 6 Reporter: Marek Schmidt Priority: Minor The "simple" example in examples/simple will produce NPE, because the SimpleAuthenticator does not call setStatus(AuthenticationStatus.FAILURE) when incorrect credentials are provided by the user. Since the example is also used in the documentation, it probably teaches a bad practice of writing custom authenticators. The example and the docs should probably be updated to contain a call to setStatus(AuthenticationStatus.FAILURE) The exception from server logs: 16:52:26,901 ERROR [org.jboss.seam.security.IdentityImpl] Login failed: java.lang.RuntimeException: java.lang.NullPointerException at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:328) [:3.0.0-SNAPSHOT] at org.jboss.seam.security.IdentityImpl.login(IdentityImpl.java:229) [:3.0.0-SNAPSHOT] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [:1.6.0_18] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [:1.6.0_18] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [:1.6.0_18] at java.lang.reflect.Method.invoke(Method.java:616) [:1.6.0_18] at org.apache.el.parser.AstValue.invoke(AstValue.java:196) [:6.0.0.Final] at org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:276) [:6.0.0.Final] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [:6.0.0.Final] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [:6.0.0.Final] at org.jboss.weld.util.el.ForwardingMethodExpression.invoke(ForwardingMethodExpression.java:43) [:6.0.0.Final] at org.jboss.weld.el.WeldMethodExpression.invoke(WeldMethodExpression.java:56) [:6.0.0.Final] at com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:102) [:2.0.3-] at javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:84) [:2.0.3-] at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:98) [:2.0.3-] at javax.faces.component.UICommand.broadcast(UICommand.java:311) [:2.0.3-] at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:781) [:2.0.3-] at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1246) [:2.0.3-] at com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:77) [:2.0.3-] at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:97) [:2.0.3-] at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:114) [:2.0.3-] at javax.faces.webapp.FacesServlet.service(FacesServlet.java:308) [:2.0.3-] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.jboss.weld.servlet.ConversationPropagationFilter.doFilter(ConversationPropagationFilter.java:67) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:274) [:6.0.0.Final] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final] at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final] at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final] at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final] at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final] at java.lang.Thread.run(Thread.java:636) [:1.6.0_18] Caused by: java.lang.NullPointerException at org.jboss.seam.security.IdentityImpl.authenticate(IdentityImpl.java:311) [:3.0.0-SNAPSHOT] ... 43 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMCRON-1) Support retry logic

by Peter Royle (JIRA)

Support retry logic ------------------- Key: SEAMCRON-1 URL: https://issues.jboss.org/browse/SEAMCRON-1 Project: Seam Cron Issue Type: Feature Request Reporter: Peter Royle Assignee: Peter Royle Support retry logic natively, allowing it to be specified declaratively. -- 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: (SEAMXML-45) Problem with empty beans.xml (in seam-conversation-spi-3.0.0.CR1)

by Matthias Unverzagt (JIRA)

Problem with empty beans.xml (in seam-conversation-spi-3.0.0.CR1) ----------------------------------------------------------------- Key: SEAMXML-45 URL: https://issues.jboss.org/browse/SEAMXML-45 Project: Seam Config Issue Type: Bug Affects Versions: 3.0.0.CR4 Reporter: Matthias Unverzagt With <seam.version>3.0.0.Final</seam.version> I got ERROR log message org.jboss.seam.config.xml.util.XmlConfigurationException: Wrong root namespace for XML config file, expected:urn:java:ee or http://java.sun.com/xml/ns/javaee found: at jar:file:/E:/.../WEB-INF/lib/seam-conversation-spi-3.0.0.CR1.jar!/META-INF/beans.xml:19 Please repair config or (to make it deployable) add namespace in empty seam-conversation-spi-3.0.0.CR1.jar/META-INF/beans.xml <beans xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://docs.jboss.org/cdi/beans_1_0.xsd"> </beans> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3837) JobExecutorServlet as seam component

by Marko Strukelj (JIRA)

JobExecutorServlet as seam component ------------------------------------ Key: JBSEAM-3837 URL: https://jira.jboss.org/jira/browse/JBSEAM-3837 Project: Seam Issue Type: Feature Request Components: BPM Affects Versions: 2.0.3.CR1 Environment: Seam 2.0.3, JBPM 3.2.2 Reporter: Marko Strukelj Priority: Optional JBPM Job Execution using JobExecutorServlet doesn't work in Seam. Attached are modified sources to turn JobExecutorServlet into a Seam component and to have it use Seam's contexts and transactions. This is probably not the best way to do it but it works for me where I'm using it. There is a proper solution in the making - see related issues. -- 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

5
6
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-49) Validate Exception Handler injections points at deploy time

by Jason Porter (JIRA)

Validate Exception Handler injections points at deploy time ----------------------------------------------------------- Key: SEAMCATCH-49 URL: https://issues.jboss.org/browse/SEAMCATCH-49 Project: Seam Catch Issue Type: Feature Request Components: Core Implementation Affects Versions: 3.0.0.Final Reporter: Jason Porter Assignee: Jason Porter We need to check if injection points in handlers are valid when we create the HandlerMethod during deployment, and fail if they are not. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMCATCH-55) Upgrade to Arquillian Alpha5

by Jason Porter (JIRA)

Upgrade to Arquillian Alpha5 ---------------------------- Key: SEAMCATCH-55 URL: https://issues.jboss.org/browse/SEAMCATCH-55 Project: Seam Catch Issue Type: Library Upgrade Reporter: Jason Porter Assignee: Jason Porter Fix For: 3.1.0.Alpha -- 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-59) @LoggedIn has wrong target

by Patrick McFarland (JIRA)

@LoggedIn has wrong target -------------------------- Key: SEAMSECURITY-59 URL: https://issues.jboss.org/browse/SEAMSECURITY-59 Project: Seam Security Issue Type: Bug Reporter: Patrick McFarland @LoggedIn security currently uses: @Target({ElementType.METHOD, ElementType.TYPE}) It should be: @Target({ElementType.FIELD, ElementType.METHOD, ElementType.TYPE}) Otherwise it cannot be used to tag pages in a @ViewConfig (since it has to tag fields in an enum in the interface) -- 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: (SEAMCONFIG-45) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMCONFIG-45 URL: https://issues.jboss.org/browse/SEAMCONFIG-45 Project: Seam Config Issue Type: Task Reporter: Jason Porter Assignee: Stuart Douglas 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: (SEAMCRON-4) Update code formatting to community formatting rules

by Jason Porter (JIRA)

Update code formatting to community formatting rules ---------------------------------------------------- Key: SEAMCRON-4 URL: https://issues.jboss.org/browse/SEAMCRON-4 Project: Seam Cron Issue Type: Task Reporter: Jason Porter Assignee: Peter Royle 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011