> I'm still confused about what you are trying to accomplish here. I would
> really appreciate it if you could take a few minutes and write down,
> without specifying a notation, the sequence of events you are trying to
> control and the variation points along that sequence.
Sure. There are three major reason why I am moving in this direction.
1) Expose as much configuration to integrators as possible, with out
complicating the system for users who do not need to muck with the
boot config.
2) Setup logging as soon as possible.
3) Provide a richer configuration lanugage.
I do not expect most users/integrators to change the sequence, but I do
expect that they might want to tweak some parameters.
What I suggest will provide a definitive configuration file for the server,
not just the service which are running inside.
I personally have not made use of the JBoss distribution layout, ever. It
has never fit in with my deployment scheme. I spent a few weeks writing a
jython/ant based system which handles setting up the environment that JBoss
expects from my layout. I have heard others with the same problem, trying
to get it read files from somewhere other than conf/xxx/** and the like.
There is no reason why we need to be strict when it comes to where these
files live, or how users tell JBoss where to find them.
Does that help, or have I just clouded the issue more?
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
