-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deployment fails since enabling CDI in 2.0.0-SNAPSHOT. #2640
Comments
Hi, I tried to debug and also simplified my project, to get an idea what's wrong, because it seems to be an problem while scanning the annotations, but i can't figure it out. May be you have an hint for me? |
Which Jackson version are you using? possibly may be related to FasterXML/jackson-modules-base#31 which is fixed in jackson 2.9.3 (although dep version of swagger is the same in rc3 and rc4); worth trying to use 2.9.3 though. Regarding your original issue with |
After switching to version 2.9.3 (we have 2.8.6) of jackson, |
I think 2.0.0-rc4 actually does have the CDI-enablement in it. Here's how I was able to upgrade Hammock: https://github.com/hammock-project/hammock/pull/125/files Notice how integrators using CDI should be able to delete pointless code since |
Oops, sorry, I was wrong... My test is lying to me! This is what our final upgrade will look like if CDI-enablement lasts until rc5, except without the |
Hi, |
The deployment of our project (ear) on Wildfly (10.0.0) runs into the following exception since we using swagger-core rc4:
15:32:41,558 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."public-rest-service-4.0.0-SNAPSHOT.war".WeldStartService: org.jboss.msc.service.StartException in service jboss.deployment.unit."public-rest-service-4.0.0-SNAPSHOT.war".WeldStartService: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.jboss.weld.exceptions.DefinitionException: WELD-000071: Managed bean with a parameterized bean class must be @dependent: class org.apache.cxf.jaxrs.provider.JAXBElementProvider
at org.jboss.weld.bean.ManagedBean.checkType(ManagedBean.java:208)
at org.jboss.weld.bean.AbstractBean.initializeAfterBeanDiscovery(AbstractBean.java:107)
at org.jboss.weld.bean.ManagedBean.initializeAfterBeanDiscovery(ManagedBean.java:122)
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:63)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at org.jboss.threads.JBossThread.run(JBossThread.java:320)
I think this happens due to the changes based on #2617.
Is there a possible workaround or a solution to this issue?
The text was updated successfully, but these errors were encountered: