From issues at jboss.org  Mon Mar  3 04:20:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 3 Mar 2014 04:20:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4910) Seam 2.3.x (JSF2) doesn't
 work with myfaces
In-Reply-To: <JIRA.12462191.1332350617000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12462191.1332350617000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12462191.1332350617000.31467.1393838447992@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-4910:
----------------------------------

    Labels: myfaces  (was: )

    
> Seam 2.3.x (JSF2) doesn't work with myfaces
> -------------------------------------------
>
>                 Key: JBSEAM-4910
>                 URL: https://issues.jboss.org/browse/JBSEAM-4910
>             Project: Seam 2
>          Issue Type: Bug
>    Affects Versions: 2.3.0.ALPHA
>            Reporter: Dupont Dupont
>              Labels: myfaces
>             Fix For: The future
>
>         Attachments: DecorateHandler.java
>
>
> When using Seam 2.3.0-SNAPSHOT, with a page containing s:decorate tag, I get 
> {code}
> Caused by: java.lang.ClassNotFoundException: com.sun.faces.facelets.tag.ui.DecorateHandler
>                 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1678)
>                 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1523)
>                 at org.jboss.seam.ui.handler.DecorateHandler.<init>(DecorateHandler.java:21)
>                 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 org.apache.myfaces.view.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.createHandler(AbstractTagLibrary.java:519)
>                 at org.apache.myfaces.view.facelets.tag.AbstractTagLibrary.createTagHandler(AbstractTagLibrary.java:98)
>                 at org.apache.myfaces.view.facelets.compiler.TagLibraryConfig$TagLibraryImpl.createTagHandler(TagLibraryConfig.java:113)
>                 at org.apache.myfaces.view.facelets.tag.CompositeTagLibrary.createTagHandler(CompositeTagLibrary.java:93)
>                 at org.apache.myfaces.view.facelets.compiler.TagUnit.createFaceletHandler(TagUnit.java:56)
>                 at org.apache.myfaces.view.facelets.compiler.TextUnit.createFaceletHandler(TextUnit.java:104)
>                 at org.apache.myfaces.view.facelets.compiler.CompilationUnit.getNextFaceletHandler(CompilationUnit.java:84)
>                 at org.apache.myfaces.view.facelets.compiler.TagUnit.getNextHandler(TagUnit.java:61)
>                 at org.apache.myfaces.view.facelets.tag.AbstractTagLibrary$ComponentConfigWrapper.getNextHandler(AbstractTagLibrary.java:431)
>                 at javax.faces.view.facelets.TagHandler.<init>(TagHandler.java:41)
> {code}
> This is due to org.jboss.seam.ui.handler.DecorateHandler in jboss-seam-ui-jsf2 using com.sun.faces.facelets.tag.ui.DecorateHandler (Mojarra class, whereas I'm using myfaces)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Mar  3 04:20:48 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 3 Mar 2014 04:20:48 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-4910) Seam 2.3.x (JSF2) doesn't
 work with myfaces
In-Reply-To: <JIRA.12462191.1332350617000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12462191.1332350617000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12462191.1332350617000.31469.1393838448143@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-4910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-4910:
----------------------------------

    Component/s: JSF Integration

    
> Seam 2.3.x (JSF2) doesn't work with myfaces
> -------------------------------------------
>
>                 Key: JBSEAM-4910
>                 URL: https://issues.jboss.org/browse/JBSEAM-4910
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.3.0.ALPHA
>            Reporter: Dupont Dupont
>              Labels: myfaces
>             Fix For: The future
>
>         Attachments: DecorateHandler.java
>
>
> When using Seam 2.3.0-SNAPSHOT, with a page containing s:decorate tag, I get 
> {code}
> Caused by: java.lang.ClassNotFoundException: com.sun.faces.facelets.tag.ui.DecorateHandler
>                 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1678)
>                 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1523)
>                 at org.jboss.seam.ui.handler.DecorateHandler.<init>(DecorateHandler.java:21)
>                 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 org.apache.myfaces.view.facelets.tag.AbstractTagLibrary$UserComponentHandlerFactory.createHandler(AbstractTagLibrary.java:519)
>                 at org.apache.myfaces.view.facelets.tag.AbstractTagLibrary.createTagHandler(AbstractTagLibrary.java:98)
>                 at org.apache.myfaces.view.facelets.compiler.TagLibraryConfig$TagLibraryImpl.createTagHandler(TagLibraryConfig.java:113)
>                 at org.apache.myfaces.view.facelets.tag.CompositeTagLibrary.createTagHandler(CompositeTagLibrary.java:93)
>                 at org.apache.myfaces.view.facelets.compiler.TagUnit.createFaceletHandler(TagUnit.java:56)
>                 at org.apache.myfaces.view.facelets.compiler.TextUnit.createFaceletHandler(TextUnit.java:104)
>                 at org.apache.myfaces.view.facelets.compiler.CompilationUnit.getNextFaceletHandler(CompilationUnit.java:84)
>                 at org.apache.myfaces.view.facelets.compiler.TagUnit.getNextHandler(TagUnit.java:61)
>                 at org.apache.myfaces.view.facelets.tag.AbstractTagLibrary$ComponentConfigWrapper.getNextHandler(AbstractTagLibrary.java:431)
>                 at javax.faces.view.facelets.TagHandler.<init>(TagHandler.java:41)
> {code}
> This is due to org.jboss.seam.ui.handler.DecorateHandler in jboss-seam-ui-jsf2 using com.sun.faces.facelets.tag.ui.DecorateHandler (Mojarra class, whereas I'm using myfaces)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Mar  3 04:22:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 3 Mar 2014 04:22:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5137) Seam Mail doesn't work
 with MyFaces implementation
In-Reply-To: <JIRA.12533734.1393838553080@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533734.1393838553080@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533734.1393838553080.31472.1393838567542@jira02.app.mwc.hst.phx2.redhat.com>

Marek Novotny created JBSEAM-5137:
-------------------------------------

             Summary: Seam Mail doesn't work with MyFaces implementation
                 Key: JBSEAM-5137
                 URL: https://issues.jboss.org/browse/JBSEAM-5137
             Project: Seam 2
          Issue Type: Bug
          Components: JSF Integration
    Affects Versions: 2.3.1.Final
            Reporter: Marek Novotny


Seam FaceletsRenderer has a class depenency to "com.sun.faces.facelets.Facelet" which does neither exist in JSF 2.2 nor in MyFaces. Because of this, the Renderer component doesn't even get instantiated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Mon Mar  3 04:24:47 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Mon, 3 Mar 2014 04:24:47 -0500 (EST)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5137) Seam Mail doesn't work
 with MyFaces implementation
In-Reply-To: <JIRA.12533734.1393838553000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12533734.1393838553000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12533734.1393838553000.31474.1393838687921@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5137:
----------------------------------

    Labels: myfaces  (was: )

    
> Seam Mail doesn't work with MyFaces implementation
> --------------------------------------------------
>
>                 Key: JBSEAM-5137
>                 URL: https://issues.jboss.org/browse/JBSEAM-5137
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Integration
>    Affects Versions: 2.3.1.Final
>            Reporter: Marek Novotny
>              Labels: myfaces
>
> Seam FaceletsRenderer has a class depenency to "com.sun.faces.facelets.Facelet" which does neither exist in JSF 2.2 nor in MyFaces. Because of this, the Renderer component doesn't even get instantiated.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Mar 14 06:04:11 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Fri, 14 Mar 2014 06:04:11 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5056) chatroom example
 occasional NPE in
 org.jboss.seam.jms.TopicSession.create(TopicSession.java:38)
In-Reply-To: <JIRA.12478419.1351784893000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12478419.1351784893000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12478419.1351784893000.16420.1394791451558@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reopened JBSEAM-5056:
-----------------------------------


    
> chatroom example occasional NPE in org.jboss.seam.jms.TopicSession.create(TopicSession.java:38)
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5056
>                 URL: https://issues.jboss.org/browse/JBSEAM-5056
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Async, Remoting
>    Affects Versions: 2.3.0.Final
>         Environment: AS 7.1.3.Final, Seam 2.3.1-SNAPSHOT, RHEL4 i386, Sun JDK 1.6.0_30
>            Reporter: Marek Schmidt
>            Assignee: Marek Novotny
>             Fix For: 2.3.2.CR1
>
>
> remoting/chatroom example functional test sometimes fail with the following error in the server log. This issue occurs only sometimes on some Jenkins slaves, I have not yet been able to reproduce the issue locally.
> {noformat}
> 09:50:47,861 ERROR [org.jboss.as.ejb3.invocation] (http-/127.0.0.1:8080-2) JBAS014134: EJB Invocation failed on component ChatRoomAction for method public abstract boolean org.jboss.seam.example.remoting.chatroom.ChatRoomActionWebRemote.connect(java.lang.String): javax.ejb.EJBException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:164) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:302) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:188) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:181) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulComponentIdInterceptor.processInvocation(StatefulComponentIdInterceptor.java:52) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.seam.example.remoting.chatroom.ChatRoomActionWebRemote$$$view3.connect(Unknown Source) [chatroom-ejb.jar:]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:32) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:43) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.javassist.tmp.java.lang.Object_$$_javassist_seam_2.connect(Object_$$_javassist_seam_2.java)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.remoting.Call.processInvocation(Call.java:208) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.Call.execute(Call.java:144) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.ExecutionHandler$1.process(ExecutionHandler.java:89) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:65) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:78) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
>     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
>     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
>     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
>     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
>     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
>     at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
>     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
>     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
>     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
>     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
>     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
>     at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
>     at org.jboss.seam.Component.newInstance(Component.java:2208) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:2034) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1996) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2414) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getValueToInject(Component.java:2366) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.injectAttributes(Component.java:1743) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.inject(Component.java:1561) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:29) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:30) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:123) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:58)
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:156) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:226) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     ... 76 more
> Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.jms.topicSession
>     at org.jboss.seam.Component.newInstance(Component.java:2208) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:2034) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1996) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1990) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1970) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1965) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.jms.TopicSession.instance(TopicSession.java:55) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.jms.ManagedTopicPublisher.create(ManagedTopicPublisher.java:53) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callComponentMethod(Component.java:2313) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callCreateMethod(Component.java:2236) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.newInstance(Component.java:2196) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     ... 119 more
> Caused by: java.lang.NullPointerException
>     at org.jboss.seam.jms.TopicSession.create(TopicSession.java:38) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callComponentMethod(Component.java:2313) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callCreateMethod(Component.java:2236) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.newInstance(Component.java:2196) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     ... 135 more
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Fri Mar 14 06:04:11 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Fri, 14 Mar 2014 06:04:11 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5056) chatroom example
 occasional NPE in
 org.jboss.seam.jms.TopicSession.create(TopicSession.java:38)
In-Reply-To: <JIRA.12478419.1351784893000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12478419.1351784893000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12478419.1351784893000.16424.1394791451851@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny closed JBSEAM-5056.
---------------------------------

    Resolution: Won't Fix


due design this won't be fixed
                
> chatroom example occasional NPE in org.jboss.seam.jms.TopicSession.create(TopicSession.java:38)
> -----------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5056
>                 URL: https://issues.jboss.org/browse/JBSEAM-5056
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Async, Remoting
>    Affects Versions: 2.3.0.Final
>         Environment: AS 7.1.3.Final, Seam 2.3.1-SNAPSHOT, RHEL4 i386, Sun JDK 1.6.0_30
>            Reporter: Marek Schmidt
>            Assignee: Marek Novotny
>             Fix For: 2.3.2.CR1
>
>
> remoting/chatroom example functional test sometimes fail with the following error in the server log. This issue occurs only sometimes on some Jenkins slaves, I have not yet been able to reproduce the issue locally.
> {noformat}
> 09:50:47,861 ERROR [org.jboss.as.ejb3.invocation] (http-/127.0.0.1:8080-2) JBAS014134: EJB Invocation failed on component ChatRoomAction for method public abstract boolean org.jboss.seam.example.remoting.chatroom.ChatRoomActionWebRemote.connect(java.lang.String): javax.ejb.EJBException: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:164) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:228) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:302) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:188) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:42) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:32) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:181) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulComponentIdInterceptor.processInvocation(StatefulComponentIdInterceptor.java:52) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:72) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.seam.example.remoting.chatroom.ChatRoomActionWebRemote$$$view3.connect(Unknown Source) [chatroom-ejb.jar:]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInvocationContext.proceed(RootInvocationContext.java:32) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.ClientSideInterceptor$1.proceed(ClientSideInterceptor.java:76) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:56) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.ejb.RemoveInterceptor.aroundInvoke(RemoveInterceptor.java:43) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.ClientSideInterceptor.invoke(ClientSideInterceptor.java:54) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.javassist.tmp.java.lang.Object_$$_javassist_seam_2.connect(Object_$$_javassist_seam_2.java)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.remoting.Call.processInvocation(Call.java:208) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.Call.execute(Call.java:144) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.ExecutionHandler$1.process(ExecutionHandler.java:89) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.ContextualHttpServletRequest.run(ContextualHttpServletRequest.java:65) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.ExecutionHandler.handle(ExecutionHandler.java:78) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.remoting.Remoting.getResource(Remoting.java:111) [jboss-seam-remoting-2.3.1-SNAPSHOT.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamResourceServlet.service(SeamResourceServlet.java:80) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final.jar:1.0.1.Final]
>     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329)
>     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:83) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.LoggingFilter.doFilter(LoggingFilter.java:60) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.IdentityFilter.doFilter(IdentityFilter.java:40) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.MultipartFilter.doFilter(MultipartFilter.java:90) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.ExceptionFilter.doFilter(ExceptionFilter.java:64) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.web.RedirectFilter.doFilter(RedirectFilter.java:45) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter$FilterChainImpl.doFilter(SeamFilter.java:69) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.servlet.SeamFilter.doFilter(SeamFilter.java:158) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:280)
>     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248)
>     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275)
>     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161)
>     at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:165)
>     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155)
>     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
>     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
>     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:372)
>     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877)
>     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679)
>     at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931)
>     at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: topicPublisher
>     at org.jboss.seam.Component.newInstance(Component.java:2208) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:2034) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1996) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2414) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getValueToInject(Component.java:2366) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.injectAttributes(Component.java:1743) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.inject(Component.java:1561) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:61) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.ConversationInterceptor.aroundInvoke(ConversationInterceptor.java:56) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:44) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:29) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:30) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:107) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptorFactory$ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptorFactory.java:123) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.WeavedInterceptor.processInvocation(WeavedInterceptor.java:53) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:36) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47)
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.jpa.interceptor.SFSBInvocationInterceptor.processInvocation(SFSBInvocationInterceptor.java:58)
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptor.processInvocation(StatefulSessionSynchronizationInterceptor.java:156) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:53) [jboss-as-ee-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:67) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
>     at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:226) [jboss-as-ejb3-7.1.3.Final.jar:7.1.3.Final]
>     ... 76 more
> Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: org.jboss.seam.jms.topicSession
>     at org.jboss.seam.Component.newInstance(Component.java:2208) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:2034) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1996) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1990) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1970) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.getInstance(Component.java:1965) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.jms.TopicSession.instance(TopicSession.java:55) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.jms.ManagedTopicPublisher.create(ManagedTopicPublisher.java:53) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callComponentMethod(Component.java:2313) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callCreateMethod(Component.java:2236) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.newInstance(Component.java:2196) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     ... 119 more
> Caused by: java.lang.NullPointerException
>     at org.jboss.seam.jms.TopicSession.create(TopicSession.java:38) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.6.0_30]
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) [rt.jar:1.6.0_30]
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) [rt.jar:1.6.0_30]
>     at java.lang.reflect.Method.invoke(Method.java:597) [rt.jar:1.6.0_30]
>     at org.jboss.seam.util.Reflections.invoke(Reflections.java:22) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.util.Reflections.invokeAndWrap(Reflections.java:144) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callComponentMethod(Component.java:2313) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.callCreateMethod(Component.java:2236) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     at org.jboss.seam.Component.newInstance(Component.java:2196) [jboss-seam.jar:2.3.1-SNAPSHOT]
>     ... 135 more
> {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Sun Mar 16 11:54:10 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Sun, 16 Mar 2014 11:54:10 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5138) styleClass and style
 attributes missing in <s:label> ui component
In-Reply-To: <JIRA.12535100.1394985192560@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535100.1394985192560@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535100.1394985192560.19833.1394985250938@jira02.app.mwc.hst.phx2.redhat.com>

Marek Novotny created JBSEAM-5138:
-------------------------------------

             Summary: styleClass and style attributes missing in <s:label> ui component
                 Key: JBSEAM-5138
                 URL: https://issues.jboss.org/browse/JBSEAM-5138
             Project: Seam 2
          Issue Type: Bug
          Components: JSF Controls
    Affects Versions: 2.3.1.Final
            Reporter: Marek Novotny
            Assignee: Marek Novotny
            Priority: Minor


s.taglib.xml in jboss-seam-ui-2.3.1.Final.jar doesn't contain styleClass and style attributes 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Sun Mar 16 11:56:10 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Sun, 16 Mar 2014 11:56:10 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5138) styleClass and style
 attributes missing in <s:label> ui component
In-Reply-To: <JIRA.12535100.1394985192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535100.1394985192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535100.1394985192000.19840.1394985370724@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5138:
----------------------------------

    Fix Version/s: 2.3.2.CR1

    
> styleClass and style attributes missing in <s:label> ui component
> -----------------------------------------------------------------
>
>                 Key: JBSEAM-5138
>                 URL: https://issues.jboss.org/browse/JBSEAM-5138
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Controls
>    Affects Versions: 2.3.1.Final
>            Reporter: Marek Novotny
>            Assignee: Marek Novotny
>            Priority: Minor
>             Fix For: 2.3.2.CR1
>
>
> s.taglib.xml in jboss-seam-ui-2.3.1.Final.jar doesn't contain styleClass and style attributes 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Sun Mar 16 11:56:10 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Sun, 16 Mar 2014 11:56:10 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5138) styleClass and style
 attributes missing in <s:label> ui component
In-Reply-To: <JIRA.12535100.1394985192000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535100.1394985192000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535100.1394985192000.19842.1394985370805@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny resolved JBSEAM-5138.
-----------------------------------

    Resolution: Done


fixed by adding core-props.xml into UILabel for RF CDK to generate those missing attributes - style and styleClass.
                
> styleClass and style attributes missing in <s:label> ui component
> -----------------------------------------------------------------
>
>                 Key: JBSEAM-5138
>                 URL: https://issues.jboss.org/browse/JBSEAM-5138
>             Project: Seam 2
>          Issue Type: Bug
>          Components: JSF Controls
>    Affects Versions: 2.3.1.Final
>            Reporter: Marek Novotny
>            Assignee: Marek Novotny
>            Priority: Minor
>             Fix For: 2.3.2.CR1
>
>
> s.taglib.xml in jboss-seam-ui-2.3.1.Final.jar doesn't contain styleClass and style attributes 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Mar 18 04:12:10 2014
From: issues at jboss.org (alexey plotnikov (JIRA))
Date: Tue, 18 Mar 2014 04:12:10 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5139) Attribute
 login-required="true" is ignored in *.page.xml file with ajax requests
In-Reply-To: <JIRA.12535213.1395130289680@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12535213.1395130289680@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12535213.1395130289680.22714.1395130330564@jira02.app.mwc.hst.phx2.redhat.com>

alexey plotnikov created JBSEAM-5139:
----------------------------------------

             Summary: Attribute login-required="true" is ignored in *.page.xml file with ajax requests
                 Key: JBSEAM-5139
                 URL: https://issues.jboss.org/browse/JBSEAM-5139
             Project: Seam 2
          Issue Type: Feature Request
    Affects Versions: 2.3.1.Final
            Reporter: alexey plotnikov


I use:
Jboss Seam 2.3.1.Final, Richfaces 4.3.5.Final.
# something.xhtml page:
{code}
<!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<ui:composition xmlns="http://www.w3.org/1999/xhtml"
                xmlns:s="http://jboss.org/schema/seam/taglib"
                xmlns:ui="http://java.sun.com/jsf/facelets"
                xmlns:f="http://java.sun.com/jsf/core"
                xmlns:h="http://java.sun.com/jsf/html"
                xmlns:rich="http://richfaces.org/rich"
                xmlns:a4j="http://richfaces.org/a4j"
                template="/layout/wide_template.xhtml">
<ui:define name="content">
<h:form>
            <a4j:commandLink execute="@form" status="common_status" render="mainList,pages" value="#{messages['pages.refresh']}"/>
.............................
{code}
# something.page.xml file:
{code}
<?xml version="1.0" encoding="UTF-8"?>
<page xmlns="http://jboss.org/schema/seam/pages"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xsi:schemaLocation="http://jboss.org/schema/seam/pages http://jboss.org/schema/seam/pages-2.3.xsd"
      login-required="true" action="#{somethingList.find}">
    <restrict>#{permissions.hasPermission('somethingList','list')}</restrict>
    <param name="order" value="#{somethingList.order}" required="false"/>
</page>
{code}
# seam component SomethingList.java:
{code}
@Name("somethingList")
@Scope(ScopeType.EVENT)
@BypassInterceptors
public class SomethingList {
.......
    @Create
    public void onCreate() {
        System.out.println("loggedIn="+ Identity.instance().isLoggedIn());
        Contexts.getSessionContext().get("obj").toString();
         //SOMETHING LOGIC
.........................
     }
....
}
{code}

Two situations:
# No ajax, usually GET request for page _something.seam_(in browser http://<server>/something.seam).
## if i logged in - everythings ok, _#\{somethingList.onCreate()\}_ will be called and component will be constructed(in server.log will be printed "_loggedIn=true_")
## if my session expires and i try to get http://<server>/something.seam i will be redirected to my login page(http://<server>/login.seam) and method  _#\{somethingList.onCreate()\}_ not will be executed - everythings ok
# With ajax(clicked a4j:commandLink on the page _something.seam_) method _#\{somethingList.onCreate()\}_ always will be called
## if i logged in, _#\{somethingList.onCreate()\}_ will be called and component will be constructed(in server.log will be printed "_loggedIn=true_")
## if my session expires(or called _#\{identity.logout\}_ on another browser tab) and i click on a4j:commandLink method _#\{somethingList.onCreate()\}_ will be called and component *NOT* will be constructed(in server.log will be printed "_loggedIn=false_" and NullPointerException) and i will be redirected to my login page(http://<server>/login.seam).

Why method _#\{somethingList.onCreate()\}_ calling on ajax reguests if user not logged in(in something.page.xml login-required="true")? I think doesn't matter ajax request or get request, in both way seam must redirects user on login page and *DO NOT* call component methods!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Mar 25 07:02:12 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 25 Mar 2014 07:02:12 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5103) Conversation after @End
 method process does not release ConversationEntry lock
In-Reply-To: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12492791.1369643485000.4803.1395745332965@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny reopened JBSEAM-5103:
-----------------------------------



still the issue in 2.3.1.Final
                
> Conversation after @End method process does not release ConversationEntry lock
> ------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5103
>                 URL: https://issues.jboss.org/browse/JBSEAM-5103
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0.Final
>            Reporter: Eiichi Nagai
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.CR1
>
>
> ConversationEntry after @End method process is removed by endRequest[1] process and does not release lock. Therefore, when there is a request duplicate with the same Conversation ID by F5 operation etc, since a lock is not released, the request has to wait till the concurrent-request-timeout even if pre-request is already completed.
> {code:title=[1] org.jboss.seam.core.Manager.java|borderStyle=solid}
> 441:   /**
> 442:    * Touch the conversation stack, destroy ended conversations, 
> 443:    * and timeout inactive conversations.
> 444:    */
> 445:   public void endRequest(Map<String, Object> session)
> 446:   {
> 447:      if ( isLongRunningConversation() )
> 448:      {
> 449:         if ( log.isDebugEnabled() )
> 450:         {
> 451:            log.debug("Storing conversation state: " + getCurrentConversationId());
> 452:         }
> 453:         touchConversationStack( getCurrentConversationIdStack() );
> 454:      }
> 455:      else
> 456:      {
> 457:         if ( log.isDebugEnabled() )
> 458:         {
> 459:            log.debug("Discarding conversation state: " + getCurrentConversationId());
> 460:         }
> 461:         //now safe to remove the entry
> => 462:         removeCurrentConversationAndDestroyNestedContexts(session);
> 463:      }
> 464:
> 465:      /*if ( !Init.instance().isClientSideConversations() ) 
> 466:      {*/
> 467:         // difficult question: is it really safe to do this here?
> 468:         // right now we do have to do it after committing the Seam
> 469:         // transaction because we can't close EMs inside a txn
> 470:         // (this might be a bug in HEM)
> 471:         Manager.instance().conversationTimeout(session);
> 472:      //}
> 473:   }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Mar 25 07:02:13 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 25 Mar 2014 07:02:13 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5103) Conversation after @End
 method process does not release ConversationEntry lock
In-Reply-To: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12492791.1369643485000.4806.1395745333103@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5103:
----------------------------------


    
> Conversation after @End method process does not release ConversationEntry lock
> ------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5103
>                 URL: https://issues.jboss.org/browse/JBSEAM-5103
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0.Final
>            Reporter: Eiichi Nagai
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.CR1
>
>
> ConversationEntry after @End method process is removed by endRequest[1] process and does not release lock. Therefore, when there is a request duplicate with the same Conversation ID by F5 operation etc, since a lock is not released, the request has to wait till the concurrent-request-timeout even if pre-request is already completed.
> {code:title=[1] org.jboss.seam.core.Manager.java|borderStyle=solid}
> 441:   /**
> 442:    * Touch the conversation stack, destroy ended conversations, 
> 443:    * and timeout inactive conversations.
> 444:    */
> 445:   public void endRequest(Map<String, Object> session)
> 446:   {
> 447:      if ( isLongRunningConversation() )
> 448:      {
> 449:         if ( log.isDebugEnabled() )
> 450:         {
> 451:            log.debug("Storing conversation state: " + getCurrentConversationId());
> 452:         }
> 453:         touchConversationStack( getCurrentConversationIdStack() );
> 454:      }
> 455:      else
> 456:      {
> 457:         if ( log.isDebugEnabled() )
> 458:         {
> 459:            log.debug("Discarding conversation state: " + getCurrentConversationId());
> 460:         }
> 461:         //now safe to remove the entry
> => 462:         removeCurrentConversationAndDestroyNestedContexts(session);
> 463:      }
> 464:
> 465:      /*if ( !Init.instance().isClientSideConversations() ) 
> 466:      {*/
> 467:         // difficult question: is it really safe to do this here?
> 468:         // right now we do have to do it after committing the Seam
> 469:         // transaction because we can't close EMs inside a txn
> 470:         // (this might be a bug in HEM)
> 471:         Manager.instance().conversationTimeout(session);
> 472:      //}
> 473:   }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Mar 25 07:02:13 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 25 Mar 2014 07:02:13 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5103) Conversation after @End
 method process does not release ConversationEntry lock
In-Reply-To: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12492791.1369643485000.4809.1395745333241@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5103:
----------------------------------

    Affects Version/s: 2.3.1.Final

    
> Conversation after @End method process does not release ConversationEntry lock
> ------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5103
>                 URL: https://issues.jboss.org/browse/JBSEAM-5103
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0.Final, 2.3.1.Final
>            Reporter: Eiichi Nagai
>            Assignee: Marek Novotny
>             Fix For: 2.3.1.CR1
>
>
> ConversationEntry after @End method process is removed by endRequest[1] process and does not release lock. Therefore, when there is a request duplicate with the same Conversation ID by F5 operation etc, since a lock is not released, the request has to wait till the concurrent-request-timeout even if pre-request is already completed.
> {code:title=[1] org.jboss.seam.core.Manager.java|borderStyle=solid}
> 441:   /**
> 442:    * Touch the conversation stack, destroy ended conversations, 
> 443:    * and timeout inactive conversations.
> 444:    */
> 445:   public void endRequest(Map<String, Object> session)
> 446:   {
> 447:      if ( isLongRunningConversation() )
> 448:      {
> 449:         if ( log.isDebugEnabled() )
> 450:         {
> 451:            log.debug("Storing conversation state: " + getCurrentConversationId());
> 452:         }
> 453:         touchConversationStack( getCurrentConversationIdStack() );
> 454:      }
> 455:      else
> 456:      {
> 457:         if ( log.isDebugEnabled() )
> 458:         {
> 459:            log.debug("Discarding conversation state: " + getCurrentConversationId());
> 460:         }
> 461:         //now safe to remove the entry
> => 462:         removeCurrentConversationAndDestroyNestedContexts(session);
> 463:      }
> 464:
> 465:      /*if ( !Init.instance().isClientSideConversations() ) 
> 466:      {*/
> 467:         // difficult question: is it really safe to do this here?
> 468:         // right now we do have to do it after committing the Seam
> 469:         // transaction because we can't close EMs inside a txn
> 470:         // (this might be a bug in HEM)
> 471:         Manager.instance().conversationTimeout(session);
> 472:      //}
> 473:   }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

From issues at jboss.org  Tue Mar 25 07:02:13 2014
From: issues at jboss.org (Marek Novotny (JIRA))
Date: Tue, 25 Mar 2014 07:02:13 -0400 (EDT)
Subject: [seam-issues] [JBoss JIRA] (JBSEAM-5103) Conversation after @End
 method process does not release ConversationEntry lock
In-Reply-To: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12492791.1369643485000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12492791.1369643485000.4812.1395745333374@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/JBSEAM-5103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marek Novotny updated JBSEAM-5103:
----------------------------------

    Fix Version/s:     (was: 2.3.1.CR1)

    
> Conversation after @End method process does not release ConversationEntry lock
> ------------------------------------------------------------------------------
>
>                 Key: JBSEAM-5103
>                 URL: https://issues.jboss.org/browse/JBSEAM-5103
>             Project: Seam 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.3.0.Final, 2.3.1.Final
>            Reporter: Eiichi Nagai
>            Assignee: Marek Novotny
>
> ConversationEntry after @End method process is removed by endRequest[1] process and does not release lock. Therefore, when there is a request duplicate with the same Conversation ID by F5 operation etc, since a lock is not released, the request has to wait till the concurrent-request-timeout even if pre-request is already completed.
> {code:title=[1] org.jboss.seam.core.Manager.java|borderStyle=solid}
> 441:   /**
> 442:    * Touch the conversation stack, destroy ended conversations, 
> 443:    * and timeout inactive conversations.
> 444:    */
> 445:   public void endRequest(Map<String, Object> session)
> 446:   {
> 447:      if ( isLongRunningConversation() )
> 448:      {
> 449:         if ( log.isDebugEnabled() )
> 450:         {
> 451:            log.debug("Storing conversation state: " + getCurrentConversationId());
> 452:         }
> 453:         touchConversationStack( getCurrentConversationIdStack() );
> 454:      }
> 455:      else
> 456:      {
> 457:         if ( log.isDebugEnabled() )
> 458:         {
> 459:            log.debug("Discarding conversation state: " + getCurrentConversationId());
> 460:         }
> 461:         //now safe to remove the entry
> => 462:         removeCurrentConversationAndDestroyNestedContexts(session);
> 463:      }
> 464:
> 465:      /*if ( !Init.instance().isClientSideConversations() ) 
> 466:      {*/
> 467:         // difficult question: is it really safe to do this here?
> 468:         // right now we do have to do it after committing the Seam
> 469:         // transaction because we can't close EMs inside a txn
> 470:         // (this might be a bug in HEM)
> 471:         Manager.instance().conversationTimeout(session);
> 472:      //}
> 473:   }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira