June 2013 - seam-issues - Jboss List Archives

[JBoss JIRA] (JBSEAM-5111) seambay example fails to deploy on EAP 6.1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5111?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5111: ------------------------------------------------- Tomas Remes <tremes(a)redhat.com> changed the Status of [bug 961249|https://bugzilla.redhat.com/show_bug.cgi?id=961249] from ON_QA to VERIFIED > seambay example fails to deploy on EAP 6.1 > ------------------------------------------ > > Key: JBSEAM-5111 > URL: https://issues.jboss.org/browse/JBSEAM-5111 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.1 > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > seambay example fails to deploy on EAP 6.1 because of unhandled LinkageError caused by the GWT servlet missing dependency. > The root of the problem is that in several places where Seam catches ClassNotFoundException, NoClassDefFoundError, ... it doesn't catch the general LinkageError, which is thrown in these cases by the EAP 6.1 classloader. > {CODE} > 12:00:12,303 WARN [org.jboss.seam.integration.jbossas.vfs.VFSScanner] (ServerService Thread Pool -- 61) Cannot read resource: META-INF/components.xml: java.io.IOException > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleItem(VFSScanner.java:212) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleRoot(VFSScanner.java:190) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.scanResources(VFSScanner.java:153) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) [:1.7.0_19] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_19] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_19] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleItem(VFSScanner.java:208) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > ... 17 more > Caused by: java.lang.LinkageError: Failed to link org/jboss/seam/remoting/gwt/GWTService (Module "deployment.seam-seambay.ear:main" from Service Module Loader) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_19] > at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0_19] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.seam.deployment.ClassDescriptor.<init>(ClassDescriptor.java:30) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.getClassDescriptor(AbstractScanner.java:125) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.handle(AbstractScanner.java:67) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.handle(AbstractScanner.java:97) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner.handle(AbstractScanner.java:225) [jboss-seam.jar:2.3.1.CR1] > ... 21 more > Caused by: java.lang.NoClassDefFoundError: com/google/gwt/user/server/rpc/SerializationPolicyProvider > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_19] > at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0_19] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final-redhat-1] > ... 46 more > Caused by: java.lang.ClassNotFoundException: com.google.gwt.user.server.rpc.SerializationPolicyProvider from [Module "deployment.seam-seambay.ear:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > ... 50 more > 12:00:12,331 INFO [org.jboss.seam.init.Initialization] (ServerService Thread Pool -- 61) reading /WEB-INF/components.xml > 12:00:12,374 INFO [org.jboss.seam.init.Initialization] (ServerService Thread Pool -- 61) reading properties from: /seam.properties > 12:00:12,408 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init > 12:00:12,430 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: aargh, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.Aargh > 12:00:12,437 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionAction, scope: CONVERSATION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionAction > 12:00:12,467 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionDetail, scope: EVENT, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionDetailAction > 12:00:12,479 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionEnd, scope: EVENT, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionEndAction > 12:00:12,492 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionSearch, scope: SESSION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionSearchAction > 12:00:12,541 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/seam-seambay]] (ServerService Thread Pool -- 61) JBWEB000287: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.RuntimeException: Could not create Component: auctionService > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1271) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1187) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.init(Initialization.java:806) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.lang.IllegalArgumentException: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName: auctionService > at org.jboss.seam.Component.getJndiName(Component.java:456) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.Component.<init>(Component.java:233) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.Component.<init>(Component.java:205) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1255) [jboss-seam.jar:2.3.1.CR1] > ... 15 more > {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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-5111) seambay example fails to deploy on EAP 6.1

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-5111?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBSEAM-5111: ------------------------------------------------- Tomas Remes <tremes(a)redhat.com> made a comment on [bug 961249|https://bugzilla.redhat.com/show_bug.cgi?id=961249] Verified on 2.3.0.ER1 release. > seambay example fails to deploy on EAP 6.1 > ------------------------------------------ > > Key: JBSEAM-5111 > URL: https://issues.jboss.org/browse/JBSEAM-5111 > Project: Seam 2 > Issue Type: Bug > Components: Core > Affects Versions: 2.3.1.CR1 > Environment: EAP 6.1 > Reporter: Marek Schmidt > Assignee: Marek Novotny > Priority: Critical > Fix For: 2.3.2.CR1 > > > seambay example fails to deploy on EAP 6.1 because of unhandled LinkageError caused by the GWT servlet missing dependency. > The root of the problem is that in several places where Seam catches ClassNotFoundException, NoClassDefFoundError, ... it doesn't catch the general LinkageError, which is thrown in these cases by the EAP 6.1 classloader. > {CODE} > 12:00:12,303 WARN [org.jboss.seam.integration.jbossas.vfs.VFSScanner] (ServerService Thread Pool -- 61) Cannot read resource: META-INF/components.xml: java.io.IOException > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleItem(VFSScanner.java:212) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleRoot(VFSScanner.java:190) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.scanResources(VFSScanner.java:153) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > at org.jboss.seam.deployment.StandardDeploymentStrategy.scan(StandardDeploymentStrategy.java:119) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.create(Initialization.java:131) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) [:1.7.0_19] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_19] > at java.lang.reflect.Method.invoke(Method.java:601) [rt.jar:1.7.0_19] > at org.jboss.seam.integration.jbossas.vfs.VFSScanner.handleItem(VFSScanner.java:208) [jboss-seam-int.jar:6.0.0.GA-redhat-2] > ... 17 more > Caused by: java.lang.LinkageError: Failed to link org/jboss/seam/remoting/gwt/GWTService (Module "deployment.seam-seambay.ear:main" from Service Module Loader) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_19] > at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0_19] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.seam.deployment.ClassDescriptor.<init>(ClassDescriptor.java:30) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.getClassDescriptor(AbstractScanner.java:125) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.handle(AbstractScanner.java:67) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner$Handler.handle(AbstractScanner.java:97) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.deployment.AbstractScanner.handle(AbstractScanner.java:225) [jboss-seam.jar:2.3.1.CR1] > ... 21 more > Caused by: java.lang.NoClassDefFoundError: com/google/gwt/user/server/rpc/SerializationPolicyProvider > at java.lang.ClassLoader.defineClass1(Native Method) [rt.jar:1.7.0_19] > at java.lang.ClassLoader.defineClass(ClassLoader.java:791) [rt.jar:1.7.0_19] > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final-redhat-1] > ... 46 more > Caused by: java.lang.ClassNotFoundException: com.google.gwt.user.server.rpc.SerializationPolicyProvider from [Module "deployment.seam-seambay.ear:main" from Service Module Loader] > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:196) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final-redhat-1] > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final-redhat-1] > ... 50 more > 12:00:12,331 INFO [org.jboss.seam.init.Initialization] (ServerService Thread Pool -- 61) reading /WEB-INF/components.xml > 12:00:12,374 INFO [org.jboss.seam.init.Initialization] (ServerService Thread Pool -- 61) reading properties from: /seam.properties > 12:00:12,408 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: org.jboss.seam.core.init, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.core.Init > 12:00:12,430 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: aargh, scope: APPLICATION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.Aargh > 12:00:12,437 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionAction, scope: CONVERSATION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionAction > 12:00:12,467 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionDetail, scope: EVENT, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionDetailAction > 12:00:12,479 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionEnd, scope: EVENT, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionEndAction > 12:00:12,492 INFO [org.jboss.seam.Component] (ServerService Thread Pool -- 61) Component: auctionSearch, scope: SESSION, type: JAVA_BEAN, class: org.jboss.seam.example.seambay.AuctionSearchAction > 12:00:12,541 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/seam-seambay]] (ServerService Thread Pool -- 61) JBWEB000287: Exception sending context initialized event to listener instance of class org.jboss.seam.servlet.SeamListener: java.lang.RuntimeException: Could not create Component: auctionService > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1271) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.installComponents(Initialization.java:1187) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.init(Initialization.java:806) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:36) [jboss-seam.jar:2.3.1.CR1] > at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1] > at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8] > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19] > at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19] > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Caused by: java.lang.IllegalArgumentException: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName: auctionService > at org.jboss.seam.Component.getJndiName(Component.java:456) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.Component.<init>(Component.java:233) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.Component.<init>(Component.java:205) [jboss-seam.jar:2.3.1.CR1] > at org.jboss.seam.init.Initialization.addComponent(Initialization.java:1255) [jboss-seam.jar:2.3.1.CR1] > ... 15 more > {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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2389) HibernatePersistenceProvider fails with java.lang.Integer version check

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2389?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2389. --------------------------------- Fix Version/s: (was: The future) Resolution: Out of Date > HibernatePersistenceProvider fails with java.lang.Integer version check > ----------------------------------------------------------------------- > > Key: JBSEAM-2389 > URL: https://issues.jboss.org/browse/JBSEAM-2389 > Project: Seam 2 > Issue Type: Bug > Components: Core > Reporter: Christian Bauer > Priority: Critical > > My entity had a version property: > @Version > @Column(name = "OBJ_VERSION", nullable = false) > protected Integer version; > In a very involved ajax reRender/conversation situation I sometimes got the following exception from HibernatePersistenceProvider: > public static void checkVersion(Object value, Session session, Object oldVersion, Object version) > { > ClassMetadata classMetadata = getClassMetadata(value, session); > VersionType versionType = (VersionType) classMetadata.getPropertyTypes()[ classMetadata.getVersionProperty() ]; > if ( !versionType.isEqual(oldVersion, version) ) > { > throw new StaleStateException("current database version number does not match passivated version number"); > } > } > This failed because oldVersion was 'null' and version was '0'. > Hibernate returned '0' from ClassMetaData.getVersion(), it looks like it can't return null, from Javadoc: Get the version number (or timestamp) from the object's version property (or return null if not versioned). > We should do a null check before asking Hibernate. > Workaround: Use primitive for version field in entity or initialize it to '0'. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3020) Links to seam and gsg of jbosstools

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3020?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3020. --------------------------------- Resolution: Done > Links to seam and gsg of jbosstools > ----------------------------------- > > Key: JBSEAM-3020 > URL: https://issues.jboss.org/browse/JBSEAM-3020 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues > Reporter: Svetlana Mukhina > Assignee: Max Rydahl Andersen > Priority: Optional > > Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3020) Links to seam and gsg of jbosstools

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3020?page=com.atlassian.jira.plugi... ] Marek Novotny commented on JBSEAM-3020: --------------------------------------- Correct link is http://docs.jboss.org/tools/latest/, so closing this issue > Links to seam and gsg of jbosstools > ----------------------------------- > > Key: JBSEAM-3020 > URL: https://issues.jboss.org/browse/JBSEAM-3020 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues > Reporter: Svetlana Mukhina > Assignee: Max Rydahl Andersen > Priority: Optional > > Looking through the guide http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/index.html I've found a chapter http://docs.jboss.com/seam/2.0.2.GA/reference/en-US/html/gettingstartedwi... that overlapping with some of our guides - http://docs.jboss.org/tools/2.1.0.CR1/en/seam/publish/en-US/html/index.html and http://docs.jboss.org/tools/2.1.0.CR1/en/GettingStartedGuide/publish/en-U..., maybe it will be good to add links in the chapter referring to these 2 guides where a user could find more information on the topic? -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3079) Building Seam examples should not require internet connection

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3079?page=com.atlassian.jira.plugi... ] Marek Novotny reopened JBSEAM-3079: ----------------------------------- > Building Seam examples should not require internet connection > ------------------------------------------------------------- > > Key: JBSEAM-3079 > URL: https://issues.jboss.org/browse/JBSEAM-3079 > Project: Seam 2 > Issue Type: Task > Components: Build, Examples > Affects Versions: 2.0.2.SP1, 2.1.0.A1 > Reporter: Jay Balunas > Priority: Trivial > > There are currently two cases: > Trinidad for the seamdiscs example > el-ri.jar for the hibernate and jpa examples > This can be added as optional dependencies and included with the distribution. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3079) Building Seam examples should not require internet connection

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3079?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3079. --------------------------------- Resolution: Out of Date > Building Seam examples should not require internet connection > ------------------------------------------------------------- > > Key: JBSEAM-3079 > URL: https://issues.jboss.org/browse/JBSEAM-3079 > Project: Seam 2 > Issue Type: Task > Components: Build, Examples > Affects Versions: 2.0.2.SP1, 2.1.0.A1 > Reporter: Jay Balunas > Priority: Trivial > > There are currently two cases: > Trinidad for the seamdiscs example > el-ri.jar for the hibernate and jpa examples > This can be added as optional dependencies and included with the distribution. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-3079) Building Seam examples should not require internet connection

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-3079?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-3079. --------------------------------- Fix Version/s: (was: The future) Resolution: Won't Fix Seam examples uses Maven so offline mode can work if you download all dependencies first. > Building Seam examples should not require internet connection > ------------------------------------------------------------- > > Key: JBSEAM-3079 > URL: https://issues.jboss.org/browse/JBSEAM-3079 > Project: Seam 2 > Issue Type: Task > Components: Build, Examples > Affects Versions: 2.0.2.SP1, 2.1.0.A1 > Reporter: Jay Balunas > Priority: Trivial > > There are currently two cases: > Trinidad for the seamdiscs example > el-ri.jar for the hibernate and jpa examples > This can be added as optional dependencies and included with the distribution. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2730) Jetty reference guide chapter with and without Jboss Embedded

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2730?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2730. --------------------------------- Resolution: Out of Date JBoss Embedded was removed from Seam 2.3 > Jetty reference guide chapter with and without Jboss Embedded > ------------------------------------------------------------- > > Key: JBSEAM-2730 > URL: https://issues.jboss.org/browse/JBSEAM-2730 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues, Platform interoperability > Affects Versions: 2.0.1.GA, 2.1.0.A1 > Reporter: Jay Balunas > Priority: Minor > > User requested reference guide chapter for Jetty with and without Jboss Embedded. > Quote: > "Jetty, with and without Jboss Embedded. Especially how to use mvn jetty:run to test stuff during development." > Comment: > http://in.relation.to/Bloggers/DeployingSeamToVariousApplicationServers#c... -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBSEAM-2333) Move cluster documentation into a separate chapter

by Marek Novotny (JIRA)

[ https://issues.jboss.org/browse/JBSEAM-2333?page=com.atlassian.jira.plugi... ] Marek Novotny closed JBSEAM-2333. --------------------------------- Resolution: Out of Date already there http://docs.jboss.org/seam/2.3.1.CR1/reference/html_single/index.html#Clu... > Move cluster documentation into a separate chapter > -------------------------------------------------- > > Key: JBSEAM-2333 > URL: https://issues.jboss.org/browse/JBSEAM-2333 > Project: Seam 2 > Issue Type: Task > Components: Documentation Issues > Affects Versions: 2.0.0.GA > Reporter: Thorsten Kunz > Priority: Minor > > Right now the information about what to consider when Seam is being used in a clustered environment is scattered all over the docs. A note here, a note there - always in the context of the topic. What about putting all this information into a separate chapter "Seam and clustering" or something like that? This way it would be easier for people to find all the best practices if Seam is to be used in a cluster in one place. -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2013