[wildfly-dev] Regression in Java EE 7 HOL

Eduardo Sant´Ana da Silva eduardo.santanadasilva at gmail.com
Wed Nov 26 17:12:54 EST 2014


Arun,

I got rid of this error implementing the Serializable interface on the bean
that you specified.

              public class Booking implements Serializable {

But there are other errors that probably is related with what Stuart said:


org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied
dependencies for type JMSContext with qualifiers @Default

  at injection point [BackedAnnotatedField] @Inject
org.javaee7.movieplex7.points.ReceivePointsBean.context

  at
org.javaee7.movieplex7.points.ReceivePointsBean.context(ReceivePointsBean.java:0)

...


Regards,
Eduardo Sant'Ana da Silva

2014-11-26 19:20 GMT-02:00 Stuart Douglas <stuart.w.douglas at gmail.com>:

> 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.
>
> I think this is a Weld bug, but Jozef (in CC) would know more.
>
> Stuart
>
> On Thu Nov 27 2014 at 7:25:31 AM Arun Gupta <arun.gupta at gmail.com> wrote:
>
>> Java EE 7 HOL is failing to deploy on WildFly 8.2:
>>
>> 12:08:38,801 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8)
>> MSC000001: Failed to start service
>> jboss.deployment.unit."movieplex7-1.0-SNAPSHOT.war".WeldStartService:
>> org.jboss.msc.service.StartException in service
>> jboss.deployment.unit."movieplex7-1.0-SNAPSHOT.war".WeldStartService:
>> Failed to start service
>>
>> at
>> org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
>> [jboss-msc-1.2.2.Final.jar:1.2.2.Final]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>> [rt.jar:1.8.0_20]
>>
>> at
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>> [rt.jar:1.8.0_20]
>>
>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20]
>>
>> 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]
>>
>> at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:203)
>>
>> at
>> org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:105)
>>
>> at
>> org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:113)
>>
>> at
>> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:136)
>>
>> at
>> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$AfterBeanDiscoveryInitializerFactory.doWork(ConcurrentBeanDeployer.java:127)
>>
>> at
>> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:60)
>>
>> at
>> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:53)
>>
>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>> [rt.jar:1.8.0_20]
>>
>> ... 3 more
>>
>>
>> Its complaining for the bean defined at:
>>
>>
>> https://github.com/javaee-samples/javaee7-hol/blob/master/solution/movieplex7/src/main/java/org/javaee7/movieplex7/booking/Booking.java
>>
>> This has worked, and is still working fine, on WildFly 8.1.
>>
>> Thoughts ?
>>
>> Arun
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>



-- 
__________________________
Eduardo Sant'Ana da Silva - Dr.
Pesquisador / Consultor de TI
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/wildfly-dev/attachments/20141126/28cafe8e/attachment.html 


More information about the wildfly-dev mailing list