Hey,
> 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.
>
I think Jules is aware of that. He doesn't want to make wrapper if
possible.
> 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.
>
I dont think the problem is in his notification propagation. Call it
the "problem" or not - ServiceControl withouth checking for any
type (org.jboss.util.Service) adds all registered MBeans (through
notification callback) to the list of MBeans that it then uses to invoke
(through MBeanServer) MBean.init(), Mbean.start()..... and then the result
is obvious.
Vlada
> 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
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
