> Most services using the conf directory are just doing a
> ClassLoader.getResource() so overriding the conf with a user
> specific one means there is a directory in the classpath
> search order ahead of the default. This places restrictions
Yes.
> on the class loader implementation, and if you are talking
Why? This would be our classloader that we setup during the micro-kernel
startup: instead of simply setting one, we would possibly set two. In
org.jboss.system.server.ServerImpl.initBootLibraries():
list.add(config.getServerConfigURL());
We would add another one before, if a directory if specified. I guess the
order of the UCL is kept intact, right?
> > Yes, but this information could be extracted from a
> standard meta-data
> > file that could be provided by the service in itself (or
> its DD). For
> > simple engine, the attributes that can be overriden are the mbeans
> > attributes whereas for more complex engines, "this" should
> be provided by the service.
> > "this" means both the XSLT engine configuration AND the list of
> > "attributes".
> Right, but the point is, what data is available to set by the
> end user depends on this service level metadata. This
> ultimately either entails looking at what xsl variables are
> being used or yet another level of metadata that defines the
> implicit attributes used in nested configurations. The latter
> is required as well for any admin console that is going to
> provide a meaningful view into the configuration of a
> non-trival mbean like the web container.
I was thinking about the second solution (yet another level of metadata).
> I agree there needs to be a roadmap, I don't agree that these
> are transparent changes that can be added to 3.2.
I think these are transparent to 3.2:
- adding an optional conf "bis" folder for overloading conf file doesn't
impact already running servers
- providing an extension of the BM that would provide a more meaningfull
interface doesn't impace the existing BM (simply another version: simply
pick the one that fits your needs)
What is obviously not transparent for 3.2 is the startup management of
services (the Activation Manager).
Cheers,
Sacha
-------------------------------------------------------
This SF.Net email sponsored by: ApacheCon 2003,
16-19 November in Las Vegas. Learn firsthand the latest
developments in Apache, PHP, Perl, XML, Java, MySQL,
WebDAV, and more! http://www.apachecon.com/
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
