0 Replies Latest reply on Nov 24, 2016 8:36 AM by Guillermo L

    Does exclusions and dependencies on top level deployment "inherited" by sub deployments?

    Guillermo L Newbie

      Hi,

      After I read the article Class Loading in WildFly - WildFly 10 - Project Documentation Editor  I'm still a bit lost regarding some features of jboss-deployment-structure.xml. Asumming I have an ear deployment such as the following:

       

      myapp.ear

          |--mywebapp.war

          |

          |--myejb.jar

          |

          |---lib

              |---lib1.jar

              |---lib2.jar

       

      Say for example that I add some exclusions and dependencies as the following:

       

      <jboss-deployment-structure xmlns="urn:jboss:deployment-structure:1.3">

          <deployment>

              <dependencies>

                     <module name="imported-module" />

              </dependencies>

         </deployment>

      <exclusions>

          <module name="excluded-module" />

      </exclusions>

      <sub-deployment name="myejb.jar">

      </sub-deployment>

      <sub-deployment name="mywebapp.war">

      </sub-deployment>

       

      As I understand the imported dependencies within the "deployment" apply to libraries within the "lib" module and I believe they should be available to the sub deployments but the documentation is not that clear for me. Furthermore I'm wondering what happens with the exclusions. I'd say that should only apply to the module in which it has been defined so I need help to confirm my assumptions and/or clarify my understanding so my questions are:

       

      1) Should the imported-module be available to all sub-deployments?

      2) Should the excluded-module be excluded from all sub-deployments?

       

      Thanks for your help!