4 Replies Latest reply on Jul 3, 2008 1:26 AM by jaikiran

    JBoss5CR1- Changes to nested deployments redeploys the entir

    jaikiran

      Operating System : Windows 2003
      Java version : Sun Java 1.5
      JBoss version : JBoss - 5 CR1

      I have an (exploded) EAR which contains an jar file (for EJB3 artifacts) and a war file. The EAR, the jar and the war are all exploded:

      ZEJB3Persistence.ear
       |
       |
       |--- META-INF
       | |
       | |--- application.xml
       | |--- jboss-app.xml
       |
       |
       |--- myapp_ejb3.jar (ejb module)
       | |
       | |--- META-INF
       | | |
       | | |--- persistence.xml
       |
       |
       |--- myapp.jar (java module)
       |
       |--- myapp.war (war module)
      


      The application.xml contents are as follows:

      <?xml version="1.0" encoding="UTF-8"?>
      
      <application>
       <display-name>MyEJB3</display-name>
       <module>
       <web>
       <web-uri>myapp.war</web-uri>
       <context-root>/EJB3Persistence</context-root>
       </web>
       </module>
       <module>
       <ejb>myapp_ejb3.jar</ejb>
       </module>
       <module>
       <java>myapp.jar</java>
       </module>
      
      </application>


      The jboss-app.xml for classloader configuration:

      <jboss-app>
       <loader-repository>
       org.myapp:loader=EJB3PersistenceClassloader
       <loader-repository-config>
       java2ParentDelegation=false
       </loader-repository-config>
       </loader-repository>
      
      
      </jboss-app>
      


      Now when i "touch" the *persistence.xml* file, which belongs to myapp_ejb3.jar (inside the EAR), the entire (EAR) application redeploys.

      Is this expected? As far as i know, changes to only application.xml should have triggered the redeployment.