What's the full stack? if you use an old camel-cdi (you didnt mention it) then several versions were buggy and only few weld versions were supported.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://blog-rmannibucau.rhcloud.com> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory <https://javaeefactory-rmannibucau.rhcloud.com> 2017-02-24 17:08 GMT+01:00 syadav <b.srisai...@gmail.com>: > if I am using cxf:bean, it is giving below error. > For your information the same application worked in glassfish server > without > any changes even no exclusions and with cxfbean: route. > > 2017-02-24 21:32:35 DEBUG DefaultCamelContext:865 - Adding routes from > builder: Routes: [] > SEVERE - CDI Beans module deployment failed > org.apache.webbeans.exception.WebBeansDeploymentException: Error while > sending SystemEvent to a CDI > Extension! > org.apache.webbeans.portable.events.discovery. > AfterDeploymentValidationImpl@df1b9a > at > org.apache.webbeans.event.NotificationManager.fireEvent( > NotificationManager.java:697) > at > org.apache.webbeans.container.BeanManagerImpl.fireEvent( > BeanManagerImpl.java:485) > at > org.apache.webbeans.container.BeanManagerImpl.fireLifecycleEvent( > BeanManagerImpl.java:480 > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-CXF-in-tomee-tp5794355p5794446.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
