[JBoss JIRA] (WFLY-1406) Hibernate cannot process package-info.java any more
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-1406?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-1406:
------------------------------------
That sounds promising [~juergen.zimmermann]!
Sounds like you will likely soon have a small Hibernate patch to contribute! Let me know if you need further help with building Hibernate to try your change.
Could you also create a https://hibernate.onjira.com/browse/HHH jira as well?
Thanks for solving this!
> Hibernate cannot process package-info.java any more
> ---------------------------------------------------
>
> Key: WFLY-1406
> URL: https://issues.jboss.org/browse/WFLY-1406
> Project: WildFly
> Issue Type: Feature Request
> Components: JPA / Hibernate
> Affects Versions: 8.0.0.Alpha2
> Reporter: Juergen Zimmermann
> Attachments: javap.log, server.log, server.log.zip, shop2.war, tar.log
>
>
> I tried the snapshot which contains Hibernate 4.3.0.Beta2. However, package-info.java files are causing problems. For instance, the package de.shop.artikelverwaltung.domain has a package-info.java which causes a NoClassDefFoundError:
> "IllegalName: de/shop/artikelverwaltung/domain.package-info". Please see the stacktrace below.
> Here is an example for package-info.java which was working with WildFly 8.0.0.Alpha1:
> @XmlAccessorType(FIELD)
> @Vetoed
> package de.shop.artikelverwaltung.domain;
> import static javax.xml.bind.annotation.XmlAccessType.FIELD;
> import javax.enterprise.inject.Vetoed;
> import javax.xml.bind.annotation.XmlAccessorType;
> The stacktrace:
> ...
> 09:29:53,880 WARN [org.jboss.modules] Failed to define class de/shop/artikelverwaltung/domain.package-info in Module "deployment.shop2.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link de/shop/artikelverwaltung/domain/package-info (Module "deployment.shop2.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:427) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:260) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:75) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.Module.loadModuleClass(Module.java:526) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:188) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:444) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:432) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:374) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:119) [jboss-modules.jar:1.2.0.Final]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl$AggregatedClassLoader.findClass(ClassLoaderServiceImpl.java:218) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:423) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356) [rt.jar:1.7.0_21]
> at org.hibernate.annotations.common.util.ReflectHelper.classForName(ReflectHelper.java:160) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.packageForName(JavaReflectionManager.java:121) [hibernate-commons-annotations-4.0.2.Final.jar:4.0.2.Final]
> at org.hibernate.cfg.AnnotationBinder.bindPackage(AnnotationBinder.java:262) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.cfg.Configuration.addPackage(Configuration.java:792) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.buildHibernateConfiguration(EntityManagerFactoryBuilderImpl.java:1174) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:839) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl$4.perform(EntityManagerFactoryBuilderImpl.java:836) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.boot.registry.classloading.internal.ClassLoaderServiceImpl.withTccl(ClassLoaderServiceImpl.java:368) [hibernate-core-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:835) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.hibernate.jpa.HibernatePersistenceProvider.createContainerEntityManagerFactory(HibernatePersistenceProvider.java:142) [hibernate-entitymanager-4.3.0.Beta2.jar:4.3.0.Beta2]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:213) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.access$800(PersistenceUnitServiceImpl.java:58) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:107) [wildfly-jpa-8.0.0.Alpha2-SNAPSHOT.jar:8.0.0.Alpha2-SNAPSHOT]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.1.0.Final.jar:2.1.0.Final]
> Caused by: java.lang.NoClassDefFoundError: IllegalName: de/shop/artikelverwaltung/domain.package-info
> at java.lang.ClassLoader.preDefineClass(ClassLoader.java:646) [rt.jar:1.7.0_21]
> at java.lang.ClassLoader.defineClass(ClassLoader.java:785) [rt.jar:1.7.0_21]
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:344) [jboss-modules.jar:1.2.0.Final]
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:422) [jboss-modules.jar:1.2.0.Final]
> ... 28 more
--
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
12 years, 11 months
[JBoss JIRA] (WFLY-1678) Unable to load Validation support on application redeploy
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1678?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar updated WFLY-1678:
------------------------------
Affects Version/s: 8.0.0.Alpha3
> Unable to load Validation support on application redeploy
> ---------------------------------------------------------
>
> Key: WFLY-1678
> URL: https://issues.jboss.org/browse/WFLY-1678
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 8.0.0.Alpha2, 8.0.0.Alpha3
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Alpha4
>
> Attachments: server.log, server.log
>
>
> take kitchensink-ear application from quick starts
> http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/kitchensink-ear/
> after building
> run jboss-as:deploy to deploy app --> everything works
> then undeploy it with jboss-as:undeploy --> all ok
> then deploy it again jboss-as:deploy.
> this deploy will fail with
> {noformat}
> 22:51:52,682 WARN [org.jboss.resteasy.plugins.validation.ValidatorContextResolver] (MSC service thread 1-12) Unable to load Validation support: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456 Argument resolvedBean
> must not be null
> at org.jboss.weld.util.Preconditions.checkArgumentNotNull(Preconditions.java:40) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:770) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ParameterInjectionPointImpl.getValueToInject(ParameterInjectionPointImpl.java:76) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ConstructorInjectionPoint.getParameterValues(ConstructorInjectionPoint.java:138) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:68) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:86) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:173) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.createAndInjectBeans(DestructibleBeanInstance.java:53) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.<init>(DestructibleBeanInstance.java:33) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createInstance(ValidatorFactoryBean.java:205) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createConstraintValidatorFactory(ValidatorFactoryBean.java:191) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:118) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:47) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:103) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:93) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.proxies.ValidatorFactory$618047133$Proxy$_$$_WeldClientProxy.getValidator(Unknown Source)
> at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:83)
> at org.jboss.resteasy.plugins.validation.ValidatorContextResolver.getContext(ValidatorContextResolver.java:72) [resteasy-validator-provider-11-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.validation.ValidatorContextResolver.getContext(ValidatorContextResolver.java:30) [resteasy-validator-provider-11-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.<init>(ResourceMethodInvoker.java:110) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.processMethod(ResourceMethodRegistry.java:280) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.register(ResourceMethodRegistry.java:251) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:221) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:193) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:179) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:156) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:75) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:400) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:241) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) [resteasy-jaxrs-3.0.1.Final.jar:]
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:198) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.core.ManagedServlet.start(ManagedServlet.java:107) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:390) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:83)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:70)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> {noformat}
> I have also noticed that this will also fail if there was some other app previously deployed that also used similar technology stacks
--
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
12 years, 11 months
[JBoss JIRA] (WFLY-1678) Unable to load Validation support on application redeploy
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-1678?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar reassigned WFLY-1678:
---------------------------------
Assignee: Tomaz Cerar (was: Ron Sigal)
> Unable to load Validation support on application redeploy
> ---------------------------------------------------------
>
> Key: WFLY-1678
> URL: https://issues.jboss.org/browse/WFLY-1678
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, REST
> Affects Versions: 8.0.0.Alpha2
> Reporter: Tomaz Cerar
> Assignee: Tomaz Cerar
> Fix For: 8.0.0.Alpha4
>
> Attachments: server.log, server.log
>
>
> take kitchensink-ear application from quick starts
> http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/kitchensink-ear/
> after building
> run jboss-as:deploy to deploy app --> everything works
> then undeploy it with jboss-as:undeploy --> all ok
> then deploy it again jboss-as:deploy.
> this deploy will fail with
> {noformat}
> 22:51:52,682 WARN [org.jboss.resteasy.plugins.validation.ValidatorContextResolver] (MSC service thread 1-12) Unable to load Validation support: org.jboss.weld.exceptions.IllegalArgumentException: WELD-001456 Argument resolvedBean
> must not be null
> at org.jboss.weld.util.Preconditions.checkArgumentNotNull(Preconditions.java:40) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:770) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ParameterInjectionPointImpl.getValueToInject(ParameterInjectionPointImpl.java:76) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ConstructorInjectionPoint.getParameterValues(ConstructorInjectionPoint.java:138) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:68) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:86) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:173) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.createAndInjectBeans(DestructibleBeanInstance.java:53) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.DestructibleBeanInstance.<init>(DestructibleBeanInstance.java:33) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createInstance(ValidatorFactoryBean.java:205) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.createConstraintValidatorFactory(ValidatorFactoryBean.java:191) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:118) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.hibernate.validator.internal.cdi.ValidatorFactoryBean.create(ValidatorFactoryBean.java:47) [hibernate-validator-cdi-5.0.1.Final.jar:5.0.1.Final]
> at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:103) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:93) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) [weld-core-impl-2.0.2.Final.jar:2013-06-27 10:15]
> at org.jboss.weld.proxies.ValidatorFactory$618047133$Proxy$_$$_WeldClientProxy.getValidator(Unknown Source)
> at org.jboss.as.ee.beanvalidation.LazyValidatorFactory.getValidator(LazyValidatorFactory.java:83)
> at org.jboss.resteasy.plugins.validation.ValidatorContextResolver.getContext(ValidatorContextResolver.java:72) [resteasy-validator-provider-11-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.validation.ValidatorContextResolver.getContext(ValidatorContextResolver.java:30) [resteasy-validator-provider-11-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodInvoker.<init>(ResourceMethodInvoker.java:110) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.processMethod(ResourceMethodRegistry.java:280) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.register(ResourceMethodRegistry.java:251) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:221) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:193) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:179) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addResourceFactory(ResourceMethodRegistry.java:156) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.core.ResourceMethodRegistry.addPerRequestResource(ResourceMethodRegistry.java:75) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.registration(ResteasyDeployment.java:400) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.spi.ResteasyDeployment.start(ResteasyDeployment.java:241) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.init(ServletContainerDispatcher.java:112) [resteasy-jaxrs-3.0.1.Final.jar:]
> at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.init(HttpServletDispatcher.java:36) [resteasy-jaxrs-3.0.1.Final.jar:]
> at io.undertow.servlet.core.ManagedServlet$DefaultInstanceStrategy.start(ManagedServlet.java:198) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.core.ManagedServlet.start(ManagedServlet.java:107) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at io.undertow.servlet.core.DeploymentManagerImpl.start(DeploymentManagerImpl.java:390) [undertow-servlet-1.0.0.Beta1.jar:1.0.0.Beta1]
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:83)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.start(UndertowDeploymentService.java:70)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1942)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1875)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
> {noformat}
> I have also noticed that this will also fail if there was some other app previously deployed that also used similar technology stacks
--
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
12 years, 11 months
[JBoss JIRA] (DROOLS-207) Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core
by Geoffrey De Smet (JIRA)
[ https://issues.jboss.org/browse/DROOLS-207?page=com.atlassian.jira.plugin... ]
Geoffrey De Smet updated DROOLS-207:
------------------------------------
Description:
> EAP 6.1 --> kie-wb.war
> ---------------------------------------------------------
> EAP has scannotation-1.0.2-redhat-2.jar --> kie-wb has 1.0.3
> EAP has xmlschema-core-2.0.2-redhat-2.jar --> kie-wb has 2.0.3
In theory this should not be able to happen.
A dependency:tree on kie-wb show this:
{code}
[INFO] org.kie:kie-wb-webapp:war:6.1.0-SNAPSHOT
...
[INFO] +- org.jbpm:jbpm-designer-backend:jar:6.1.0-SNAPSHOT:compile
...
[INFO] | +- org.jbpm:jbpm-workitems:jar:6.1.0-SNAPSHOT:compile (version managed from 6.1.0-SNAPSHOT)
...
[INFO] | | \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.3:compile
{code}
and also
{code}
[INFO] org.kie:kie-wb-distribution-wars:pom:6.1.0-SNAPSHOT
...
[INFO] +- org.jboss.resteasy:resteasy-jaxrs:jar:2.3.6.Final:compile
[INFO] | +- org.scannotation:scannotation:jar:1.0.3:compile
{code}
Investigate if any of those artifacts aren't messing with the transitive dependency version by overwriting their version. It's also possible that the bug is on the side of EAP (if they overwrite one of their transitive dependencies with a lower version).
was:
> EAP 6.1 kie-wb.war
> ---------------------------------------------------------
> scannotation-1.0.2-redhat-2.jar --> dependency to 1.0.3
> xmlschema-core-2.0.2-redhat-2.jar --> dependency to 2.0.3
In theory this should not be able to happen.
A dependency:tree on kie-wb show this:
{code}
[INFO] org.kie:kie-wb-webapp:war:6.1.0-SNAPSHOT
...
[INFO] +- org.jbpm:jbpm-designer-backend:jar:6.1.0-SNAPSHOT:compile
...
[INFO] | +- org.jbpm:jbpm-workitems:jar:6.1.0-SNAPSHOT:compile (version managed from 6.1.0-SNAPSHOT)
...
[INFO] | | \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.3:compile
{code}
and also
{code}
[INFO] org.kie:kie-wb-distribution-wars:pom:6.1.0-SNAPSHOT
...
[INFO] +- org.jboss.resteasy:resteasy-jaxrs:jar:2.3.6.Final:compile
[INFO] | +- org.scannotation:scannotation:jar:1.0.3:compile
{code}
Investigate if any of those artifacts aren't messing with the transitive dependency version by overwriting their version. It's also possible that the bug is on the side of EAP (if they overwrite one of their transitive dependencies with a lower version).
> Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core
> ---------------------------------------------------------------------------------
>
> Key: DROOLS-207
> URL: https://issues.jboss.org/browse/DROOLS-207
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Geoffrey De Smet
> Assignee: Michael Biarnes Kiefer
> Priority: Minor
>
> > EAP 6.1 --> kie-wb.war
> > ---------------------------------------------------------
> > EAP has scannotation-1.0.2-redhat-2.jar --> kie-wb has 1.0.3
> > EAP has xmlschema-core-2.0.2-redhat-2.jar --> kie-wb has 2.0.3
> In theory this should not be able to happen.
> A dependency:tree on kie-wb show this:
> {code}
> [INFO] org.kie:kie-wb-webapp:war:6.1.0-SNAPSHOT
> ...
> [INFO] +- org.jbpm:jbpm-designer-backend:jar:6.1.0-SNAPSHOT:compile
> ...
> [INFO] | +- org.jbpm:jbpm-workitems:jar:6.1.0-SNAPSHOT:compile (version managed from 6.1.0-SNAPSHOT)
> ...
> [INFO] | | \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.3:compile
> {code}
> and also
> {code}
> [INFO] org.kie:kie-wb-distribution-wars:pom:6.1.0-SNAPSHOT
> ...
> [INFO] +- org.jboss.resteasy:resteasy-jaxrs:jar:2.3.6.Final:compile
> [INFO] | +- org.scannotation:scannotation:jar:1.0.3:compile
> {code}
> Investigate if any of those artifacts aren't messing with the transitive dependency version by overwriting their version. It's also possible that the bug is on the side of EAP (if they overwrite one of their transitive dependencies with a lower version).
--
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
12 years, 11 months
[JBoss JIRA] (DROOLS-207) Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core
by Geoffrey De Smet (JIRA)
Geoffrey De Smet created DROOLS-207:
---------------------------------------
Summary: Transitive dependencies are not in sync with EAP: scannotation and xmlschema-core
Key: DROOLS-207
URL: https://issues.jboss.org/browse/DROOLS-207
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Geoffrey De Smet
Assignee: Michael Biarnes Kiefer
Priority: Minor
> EAP 6.1 kie-wb.war
> ---------------------------------------------------------
> scannotation-1.0.2-redhat-2.jar --> dependency to 1.0.3
> xmlschema-core-2.0.2-redhat-2.jar --> dependency to 2.0.3
In theory this should not be able to happen.
A dependency:tree on kie-wb show this:
{code}
[INFO] org.kie:kie-wb-webapp:war:6.1.0-SNAPSHOT
...
[INFO] +- org.jbpm:jbpm-designer-backend:jar:6.1.0-SNAPSHOT:compile
...
[INFO] | +- org.jbpm:jbpm-workitems:jar:6.1.0-SNAPSHOT:compile (version managed from 6.1.0-SNAPSHOT)
...
[INFO] | | \- org.apache.ws.xmlschema:xmlschema-core:jar:2.0.3:compile
{code}
and also
{code}
[INFO] org.kie:kie-wb-distribution-wars:pom:6.1.0-SNAPSHOT
...
[INFO] +- org.jboss.resteasy:resteasy-jaxrs:jar:2.3.6.Final:compile
[INFO] | +- org.scannotation:scannotation:jar:1.0.3:compile
{code}
Investigate if any of those artifacts aren't messing with the transitive dependency version by overwriting their version. It's also possible that the bug is on the side of EAP (if they overwrite one of their transitive dependencies with a lower version).
--
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
12 years, 11 months