JBoss development, A new message was posted in the thread "Deployment of on-demand web applications": http://community.jboss.org/message/525556#525556 Author : Brian Stansberry Profile : http://community.jboss.org/people/bstansberry@jboss.com Message: -------------------------------------------------------------- Running in a debugger confirms that the HDScanner is treating each file inside the war as a new deployment. This doesn't happen with -Djboss.as.deployment.ondemand=true because there's a bug in the way profiles are configured for HD scanning. It only gets turned on via this bit in ProfileServiceBootstrap.start(...)         // Enable modification checks on all mutable profiles       for(ProfileKey key : profileService.getActiveProfileKeys())       {          try          {             Profile profile = profileService.getActiveProfile(key);             if(profile.isMutable() && profile instanceof MutableProfile)             {                ((MutableProfile) profile).enableModifiedDeploymentChecks(true);             }          }          catch(NoSuchProfileException ignore) { }   With -Djboss.as.deployment.ondemand=true when that code executes, the profiles for the on-demand wars are not yet "active" so the enableModifiedDeploymentChecks(true) call is never made.  With -Djboss.as.deployment.ondemand=false the profile is active and the profile is exposed to the HDScanner. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/525556#525556