-
1. Re: Wildfly 9.0.1 rejects a SAR (Service Archive) that works in Wildfly 8.1
ctomc Sep 25, 2015 1:13 PM (in response to tkummer)if you remove batch subsystem, does problem go away?
you can remove it by just commenting out whole <subsystem xmlns="urn:jboss:domain:batch:1.0">
tag from your standalone.xml
-
2. Re: Wildfly 9.0.1 rejects a SAR (Service Archive) that works in Wildfly 8.1
jamezp Sep 25, 2015 1:21 PM (in response to tkummer)The simplest solution is to just to also exclude the batch subsystem in your jboss-deployment-structure.xml. Do any of the modules in your EAR use batch?
--
James R. Perkins
-
3. Re: Wildfly 9.0.1 rejects a SAR (Service Archive) that works in Wildfly 8.1
jamezp Sep 25, 2015 8:22 PM (in response to tkummer)It seems that if any deployment in the EAR includes is marked as a weld deployment then it marks the EAR as a weld deployment and all other subdeployments are assumed to be weld deployments as well. The only real solution is to add an exclusion for the batch subsystem as well.
<sub-deployment name="auth-jmx.sar"> <exclude-subsystems> <subsystem name="batch"/> <subsystem name="weld"/> </exclude-subsystems> </sub-deployment>
--
James R. Perkins
-
4. Re: Wildfly 9.0.1 rejects a SAR (Service Archive) that works in Wildfly 8.1
thorkummer Sep 30, 2015 5:18 AM (in response to tkummer)We are not using batch so excluding that is OK. Excluding it from the sar in the ear's jboss-deployment-structure.xml works fine. Thanks for the help.