> 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).
I think we might want to use different names, as level1-6 might get a little
confusing. Perhaps we could assign these levels meaningful names:
bootstrap
system
user
Could also nest the structure for better naming too:
system/
bootstrap/
core/
db/
cluster/
jms/
user/
whatever/
samesame/
> 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?
Yikes, I hope there aren't any Linux systems that will init 6 and do
anything short of boot... I hope you mean init 5 (X11).
> 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?
I don't think that the actual notion of levels makes sence for the AD, but
seperating things for ordering certainly does.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
