There's been a lot of discussion recently about (to put it bluntly and with
slight exaggeration) chaos in the rh startup and deployment sequence.
One of the proposals was startup levels, like in linux.
One thing you can do right now is give AutoDeployer lots of directories to
watch:
<mbean code="org.jboss.deployment.AutoDeployer"
name="JBOSS-SYSTEM:service=AutoDeployer">
<attribute name="Deployers">
JBOSS-SYSTEM:service=ServiceDeployer;
JCA:service=RARDeployer;
J2EE:service=J2eeDeployer
</attribute>
<attribute name="URLs">
../deploy/level1,
../deploy/level2,
../deploy/level3
../deploy/level4,
../deploy/level5,
../deploy/level6
</attribute>
<attribute name="Timeout">
3000
</attribute>
</mbean>
(it may be necessary to invert the loop order in AutoDeployer: the needed
behaviour is that for each directory, all files should be deployed with all
available deployers, rather than for each deployer, all directories should
be scanned. I haven't checked to see which way the code is now).
Everything in level1 will be deployed, then everything in level2, etc. I
think this will give enough control over deployment order for almost all
circumstances. (I'd like examples of anything it won't work for).
Now, in Linux you can init 3 or init 6. So far you can't do this here. Is
that a valuable feature for jboss? (i.e. being able to say "deploy levels
1,2,3. Now deploy 4,5,6. Now undeploy 6, 5, 4, 3) How would it be used?
Would this be more or less convenient to use than a deployment script
facility where each script basically had a list of what is in one of these
level directories?
Thanks
david jencks
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
