|It appears to me that:
|
|JBoss does not expect MBeans both not to implement Service not to be
|statically loaded from a file.
|
|Am I wrong ?
Not entirely.
The fact that it is loaded from a file is not relevant (in fact we use the
file as the input to the Configuration Service which in its new incarnation
can instanciate and configure the beans ;-) it is programmatic.
With respect to the "Service" api, it is a bare minimum to play with in
integration. It is a wrapper pattern pure and simple. If you want to leave
all the methods empty you are welcome.
Pragmatically speaking, there needs to be a place signifying some
integration, we are a system, we are typed, we cannot de-type fully the
module integration. It carries the integration lifecycle semantics
(init/start/stop/destroy as J2ee)
In short I **really** don't want to know about your internals and if you
don't want to propagate the notification we couldn't care less. That you
don't need to do anything is swell and dandy we still require it.
marc
PS:
1- write an empty MBean wrapper pattern
2- invoke the ConfigurationService or the MBeanServer directly to
instanciate the Jetty stuff internally
3- was your point that you can't really remotely do that dynamically? if so
I am already working on a solution... (mad andy you still there?)
4- You should beware of exposing everything in JMX... you can really go
crazy
5- did you guys read HP's proposal? I hear they are reaping our stuff :(((
|
|Suggestions ?
|
|
|Jules
|
|
|
|
|
|_________________________________________________________
|Do You Yahoo!?
|Get your free @yahoo.com address at http://mail.yahoo.com
|
|
|_______________________________________________
|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
