> However it is done, does anyone want something like SysV, where there are
> different levels of services available at each runlevel, and you can do
> something like jboss-init 3 to get to having only the "level 3" services
> running?

I don't see how a SysV-like configuration helps... rather it just introduces 
new wrinkles.

Do you intent to have the server boot into these levels, starting and 
killing services in the running level?

If not, then this talk about SysV doesn't make anysense.  If you are talking 
about that, then it seems like we need to put together some more 
infrastructure to walk through those levels, starting and killing services.

I personally don't see how it will be useful.

I do however see that it would make sence to add more order to the 
organization of the deployment directory with respect to how these 
deployables get loaded.

> Is it sufficient to have more control over deployment ordering?

Don't we already have this?

> Who likes the list of directories approach?
> (either level1, level2,... or system/base system/..., user/base, user/app,
> user/final or whatever)

I would go with meaningful names rather than meaningless levels.

> Who likes the lexicographically ordered list approach?
> (one deploy directory, files named 0001boot.sar, 011jboss.sar,
> 012jetty.sar,  ..., 990app27.ear, 991userstartup.sar)

Yikes... no please, no.  Could probably support this anyways for users who 
want it, but lets not force its usage.

> (one possible problem with this is if you want to insert something between
> 780app1.ear and 782userservices.sar you have to rename stuff.  But it does
> give you more control over the ordering).

If you want real ordering, specify the order in the URL of the 
deployment unit in the AutoDeployer list.

> Hiram, I don't understand your problem with deploy dirs and different
> configurations.  Can't you have directories 

I *think* he might mean grouping rars, .ears, .wars and such... but that is 
just a guess.

--jason


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to