JBoss development,
A new message was posted in the thread "Deployment of on-demand web
applications":
http://community.jboss.org/message/525693#525693
Author : Emanuel Muckenhuber
Profile :
http://community.jboss.org/people/emuckenhuber
Message:
--------------------------------------------------------------
mailto:bstansberry@jboss.com wrote:
Fair enough. The above JIRAs are mostly to document this for later consideration so I
could move on to other stuff today.
Well i mean there is obviously something broken, i don't want to argue about that.
That HDScanner is picking up the contents of the .war is because i added some workaround
to integrate service-bindingmanager. I never thought this should be hot-deployable, so i
was wrong. However i need to validate if this is still true for some new profiles i'm
going to add - so might just remove this workaround and you would need to use a different
metadata to create this kind of profiles.
mailto:bstansberry@jboss.com wrote:
Hmm, but deploy-hasingleton is a bit of a different story. That's a profile that gets
activated after startup but is a legit hot deploy profile. For that we'd need to make
sure the JBAS-7721 problem is fixed.
Currently the activator has to take care of that e.g.
profileService.getActiveProfile(key).isMutable().enableModificationChecks(...);
HDScanning will change a bit in future. So basically i want to have a HDScanner per
"hot-deployment profile", so that they can have a separate scan-period and the
scanner can be started/stopped independently. I haven't finished the implementation
yet, so i cannot really say how this will exactly look like. I guess i can add a
"startAutomatically" flag to the scanner configuration, so that an activator
does not need to take care of that in future?
--------------------------------------------------------------
To reply to this message visit the message page:
http://community.jboss.org/message/525693#525693