0 Replies Latest reply on Aug 18, 2009 7:02 AM by Eran Kaplan

    How hot redeployment works

    Eran Kaplan Newbie


      I'm trying to understand how hot redeployment works. I'm using JBoss 4.2.0

      I've read the followings:
      - http://www.jboss.org/community/wiki/ClassLoadingConfiguration
      - http://www.jboss.org/community/wiki/jbossclassloadingusecases
      - JBoss Administration And Development Guide chapter 3

      From The JBoss Administration And Development Guide:
      --------------------------------------------------------------------- Scoping Classes
      If you need to deploy multiple versions of an application you need to use deployment based scoping. With deployment based scoping, each deployment creates its own class loader repository in the form of a HeirarchicalLoaderRepository3 that looks first to the UnifiedClassLoader3 instances of the deployment units included in the EAR before delegating to the default UnifiedLoaderRepository3.

      And now to the question:
      Does it mean that whenever JBoss identifies that my EAR has changed it creates a new HeirarchicalLoaderRepository3 and a new UCL for it and from now on new requests will be sent to the new deployed EAR?

      Is there any document / article that describes this process in depth?