Its probably related to the CDI upgrade. At a guess I would say thinks the bean is not passivation capable because of the EntityManager injection. <div><br></div><div>I think this is a Weld bug, but Jozef (in CC) would know more.</div><div><br></div><div>Stuart<br><br><div class="gmail_quote">On Thu Nov 27 2014 at 7:25:31 AM Arun Gupta &lt;<a href="mailto:arun.gupta@gmail.com">arun.gupta@gmail.com</a>&gt; wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Java EE 7 HOL is failing to deploy on WildFly 8.2:<div><br></div><div>







<p><span>12:08:38,801 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit.&quot;movieplex7-1.0-SNAPSHOT.war&quot;.WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit.&quot;movieplex7-1.0-SNAPSHOT.war&quot;.WeldStartService: Failed to start service</span></p>
<p><span><span>	</span>at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.2.Final.jar:1.2.2.Final]</span></p>
<p><span><span>	</span>at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_20]</span></p>
<p><span><span>	</span>at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_20]</span></p>
<p><span><span>	</span>at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]</span></p>
<p><span>Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-000072: Bean declaring a passivating scope must be passivation capable.  Bean:  Managed Bean [class org.javaee7.movieplex7.booking.Booking] with qualifiers [@Default @Any @Named]</span></p>
<p><span><span>	</span>at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:203)</span></p>
<p><span><span>	</span>at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:105)</span></p>
<p><span><span>	</span>at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:113)</span></p>
<p><span><span>	</span>at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:136)</span></p>
<p><span><span>	</span>at org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:127)</span></p>
<p><span><span>	</span>at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)</span></p>
<p><span><span>	</span>at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)</span></p>
<p><span><span>	</span>at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_20]</span></p>
<p><span><span>	</span>... 3 more</span></p> </div><div><br></div><div>Its complaining for the bean defined at:</div><div><br></div><div><a href="https://github.com/javaee-samples/javaee7-hol/blob/master/solution/movieplex7/src/main/java/org/javaee7/movieplex7/booking/Booking.java" target="_blank">https://github.com/javaee-samples/javaee7-hol/blob/master/solution/movieplex7/src/main/java/org/javaee7/movieplex7/booking/Booking.java</a></div><div><br></div><div>This has worked, and is still working fine, on WildFly 8.1.</div><div><br></div><div>Thoughts ? </div><div><br></div><div>Arun  <br></div>
______________________________<u></u>_________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/<u></u>mailman/listinfo/wildfly-dev</a></blockquote></div></div>