|2. The org.jboss.configuration.ConfigurationService mbean now registers all
|mbeans loaded from the jboss.jcml configuration file with the
|ServiceControl mbean.
|There is no requirement that an mbean implements the
|org.jboss.util.Service interface.

... hmmmm .... you are saying that when someone registers with us he doesn't
need to implement the interface?

|The Service interface used to register the jboss.jcml mbean with the
|ServiceControl mbean is obtained either from the implementation of the new
|org.jboss.util.ServiceFactory interface specificed via the new
|serviceFactory
|jboss.jcml mbean tag attribute,

So you can register ANY Service interface? what is the point of the SC
then... does it do any call?


|or by a dynamic proxy that determines

I can't make sense of the sentence... the dynamic proxy is from where
JDK1.3? and it generates a proxy that can call the interface you pass, but
what interface? I understand from the part below that you are talking about
the MBean itself, do you mean dynamic proxy in the 1.3 DynamicProxy
sense?...

|which if any of the init/start/stop/destroy methods the mbean
|implements using
|introspection of the mbean operations. The latter is used in the absence of
|a non-empty serviceFactory attribute.

ah a default, I like that.. so if I don't bother with all this, the proxy
determines what calls are offered by the MBean that just registered

well, you know me, if you code you code, so it goes in, but frankly it means
the integration is very heavy now... very heavy, a new class factory, a new
jcml tag, a new default... it is also programmatic... pfffffffffff and what
did we gain? an integration where brits can choose to not implement
interfaces of management? ;-)

Frankly I am not sure I like this...

but you code you code.

|Another behavior change made to the ConfigurationService is that
|it no longer reads
|the jboss-auto.jcml config file. This is now a write only file
|that does reflect
|configuration changes made at runtime, but it is no longer read on startup.


Ok so modifications of the server are lost upon restart... I already said
taht the auto stuff wasn't good so I am not complaining about the removal,
but frankly we need to put a similar functionality back in, that of
persistent configurations of the server.

overall good work man, it is getting somewhere,

marc

|
|This has been commited to the main cvs branch.
|
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development


_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to