[teiid-issues] [JBoss JIRA] (TEIID-4125) Problem with SOAP war generated in TD

Problem with SOAP war generated in TD ------------------------------------- Key: TEIID-4125 URL: https://issues.jboss.org/browse/TEIID-4125 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.12.5 Reporter: Matus Makovy Assignee: Van Halbert Priority: Critical Fix For: 9.0, 8.12.5 Attachments: ProductInfoVdb.war, Untitled.zip I don't know if this is a Teiid or Teiid Designer issue. When I generate a SOAP war from VDB and try to deploy it to server, I get following exception: {code} Deployment failed: ProductInfoVdb.war: {"outcome" : "failed", "failure-description" : {"JBAS014671: Failed services" : {"jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL" : "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"ProductInfoVdb.war\".INSTALL: JBAS018733: Failed to process phase INSTALL of deployment \"ProductInfoVdb.war\"\n Caused by: java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory\n Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory from [Module \"org.springframework.spring:main\" from local module loader @ed17bee (finder: local module finder @2a33fae0 (roots: /Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/dv,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base/.overlays/layer-base-jboss-eap-6.4.3.CP,/Users/mmakovy/server-installer/dv-6.3.0.DR3/target/jboss-eap-6.4/modules/system/layers/base))]"}}, "rolled-back" : true} {code} The whole "test script" should be accessible here: https://mojo.redhat.com/docs/DOC-995324 This happens *only with DV-6.3.0.DR3*. When I deploy this war to DV 6.2 server, everything works as expected. I attached project in zip file (Untitled.zip) and generated WAR. The WAR file was generated in TD 10.0.0.Beta2, but I tried to generate the war in 9.0.5 Designer and the result was the same. I marked this as Critical, but if it is a Designer issue I think it should be marked as blocker.