We load the jboss.jcml file with a conf.available
(org.jboss.configuration.ConfigurationService) that actually does the
following:
byte[] arr = new byte[conf.available()];
Juha, when we were in London, debugged that to work the right way so we
could demo how the remote installation worked. Juju, do you have that fix
in mind still? care to put it in?
Ok then the 3 staged stuff is obscure, why is the automated stuff done
before the normal one is unclear (because it used to overwrite the setting
done by the client, but then why keep it if it is only there to keep
"non-jcml" specified stuff, pffff.... we need to rethink that part) Ok I
will be clear, don't waste time on fixing this for now, we will rewrite the
part that deals with this.
finally the byte[] stuff is done several times and buggy in all the cases.
Is there any particular reason we "re-read" this as opposed to just passing
the first one, it seriously slows down the loading mechanisms from the web.
In fact when you try to do that from the web (as we did with Juha in London)
you realize how slow the loaders are (when they don't die as they do in this
current version).
marc
_________________
Marc Fleury, Ph.D
[EMAIL PROTECTED]
_________________
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
