I understand that the jboss.conf or boot.xml stuff was just complicating
things, though hard coding isn't the right solution. That said, I don't
really have a good solution at the moment, though I do have some ideas (of
course).
> configurability is good when it is needed, in this case it is not (imho,
> feel free to flame). Therefore "simple is the word...."
I certainly don't want to complicate, but I think we can find a simple
solution that provides excellent configurability for most (if not all)
applications.
We don't want to over simplify our systems and force user installs to be
complicated to work around the rigidity of the boot system.
* * *
Let us simplify Main even more. All it really needs todo is pull down a
url, parse it then load the core components.
As I mentioned before, lets drop the config name stuff and let the url
handle that for us:
http://configserver/default
or
http://configserver/some-other-config
We can still keep the patch stuff around, which would work the same.
At this point, we download the content of the url, which is expected to be
the boot loader .xml. The responsiblity of this is to setup the boot
classpath, then logging and then the support services for loading the
rest of the system.
It could be that this boot.xml is really the jboss-system.xml or whatever
the main config file is called, it contains some extra elements describing
the boot strapping sequence (and config options too it). If it does not
exist then we can pull a boot.xml from resource and use it as the seed, then
contiure parsing the file as normal.
I don't think that users would object to having one config file, which
listed 6 special services. It is having two files, of which one is not even
really an xml file, which caused confusion.
We could even add some app level <include> support which would allow us to
pull configs from other urls or from system resources.
This needs some more work before I would even consider moving twords it, but
I think that this is a positive direction to take this part of the system.
The goals being:
1) hook up real logging as soon as possible
2) make the boot sequence configurable
3) make the configuration selection simple
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
