Ok,
going through the org.jboss.configuration package.
got rid of jboss.jcml/jboss-auto.jcml, jboss.properties and all replaced by
a single system.xml.
why?
because these files are really the basis for the system and they describe
the system, in the boot strap sense of JBoss.
Dr JUNG, here is one for you... I realize that right now the base is very
static in the sense that we cannot really extend the MLet beyond the
initialization (ClassPathExtension relies on the contextCL). What that
means is that if you really want to change the implementation of something
in the system at run time well... you can't.
The main weakness is the reliance on the context class loader to get the
MLet, it assumes that we come with the system thread. I.e. there is no way
to come from the html adaptor and say "deploy this datasource from this
http://myserver/datasource.xml"; and that is really static... very far from
what I want for the 3.0 vision.
long story short, we were exploring the class loader stuff for the
applications only but it turns out that the first application that is
dynamic and needs to have parts of it cycled is the JBOSS-SYSTEM *itself* :)
so i will try to tackle this soon. Without this we really don't have a real
micro-kernel design with 24x7 uptime.
Right now I will finish the URL installs (lots of stuff to touch) and will
send more details on what is changed for 3.0.
regards
marcf
_________________
Marc Fleury, Ph.D
[EMAIL PROTECTED]
_________________
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
