"scott.stark(a)jboss.org" wrote : "emuckenhuber" wrote :
| | Because i think in the end there will be quite a lot of immutable profiles
(defined over xml), where you basically
| | don't have hot-deployment scanning.
| | And just the deploy/ directory and the clustering directories as hot-deployment
profiles.
| | IMHO as soon, as you define deployments in a profile, it does not make sense to
search for new content.
| |
|
| I'm not sure what your getting at with the last statement. We certainly will have
hot deployment, and so a dynamic profile is needed. I would think that the distinction
between dynamic/static should be explicit and the current code in the HDScanner that
obtains the active profiles would get the dynamic profiles
Are two different concepts getting mixed here?
1) Statically defined vs. dynamic profiles. In the former all the contents of the profile
are explicitly listed, in the latter a (set of) root URLs is defined and whatever is under
those roots becomes part of the profile. The former is largely used to define the
server's JBoss-provided capabilities, the latter provides the "drop a war in
deploy/ and it gets deployed" functionality for users.
2) Hot deployment == we monitor the profile's contents and if a file changes we
redeploy. This applies to both static and dynamic profiles. For dynamic profiles this also
includes detecting new items under the root URL and the removal of items under the root
URL.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4205990#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...