Sacha Labourey wrote:

This places restrictions 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?

The ordering of the URLs passed to a UCL is maintained (really an implementation
detail tha currently falls on the java.lang.URLClassLoader), and
the added order is a property of the UCL in the ULR, but I do not think this
is currently used in prioritizing duplicate resources. In this particular case
both conf locations are in the same UCL, but if there is yet another source of
the same configuration file in a deployment then I'm not sure we give priority
based on the added order.


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).

Ok, the first two points are doable in 3.2. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx



-------------------------------------------------------
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

Reply via email to