|
»
»
« Return to Thread: Mule Agents 2.0 Configuration
Re: Mule Agents 2.0 Configuration
by Daniel Feist
::
Rate this Message:
> > 1) Handle errors and inform user when jmx dependent agents are
> > configured and there is no jmx instance available.
>
> Current errors do provide that info already, did you have something in mind?
No, what's in 1.4 will work.
>
> > 2) If jmx-server is configured along with jmx dependent agents at the
> > same level, we need to deal with the initialization order issues. I'm
> > not sure how this was handled in 1.4, but in 2.0 it's all delegated to
> > spring (initialization oder or "depends-on" attribute maybe).
>
> In 1.4 it was following the XML-declared order. Depends-on could be the way
> to go, but see if you can derive the names of the beans to depend on. Maybe
> getting the beans of JmxAgent type from the registry? Otherwise a user has
> to specify those attributes (that is, if Spring does not preserve the
> order).
I would have to look into this, avoiding all this and at the same time
making things more intuitive is my preferred route though.
> > Only allowing the user to configure jmx dependent agents if jmx-server
> > is declared (remember jmx agents locates first, then creates) I
> > believe would be more intuitive and less error-prone for users and
> > also easier for us to manage jmx agents dependencies.
>
> The problem here is if any future agent depends on JMX, the schema has to be
> updated to support it.
Not really. Just add a <management:jmx-custom-agent/> element or
similar, the same we do everywhere else to provide extensibility..
> Not the case if they are top-level.
The same applies top-level there is no difference (at least with 2.0
style configurations). The schema would have jmx-server,
log4j-notification, publish-notification, chainsaw-notifications
agents defined in the schema as elements and a
<management:custom-agent class=""/> for additional or custom agents.
( There is a possibility that Jmx dependent agents implement an
additional interface, and have the MBeanServer set automatically
rather than each of them having to look it up, but this is debatable
and separate to the choice of configuration mechanism.)
Maybe I should get together the schema for what I suggest to better
see what I mean?
Also be interesting to know what the other 2.0 guys think...
Dan
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
> > configured and there is no jmx instance available.
>
> Current errors do provide that info already, did you have something in mind?
No, what's in 1.4 will work.
>
> > 2) If jmx-server is configured along with jmx dependent agents at the
> > same level, we need to deal with the initialization order issues. I'm
> > not sure how this was handled in 1.4, but in 2.0 it's all delegated to
> > spring (initialization oder or "depends-on" attribute maybe).
>
> In 1.4 it was following the XML-declared order. Depends-on could be the way
> to go, but see if you can derive the names of the beans to depend on. Maybe
> getting the beans of JmxAgent type from the registry? Otherwise a user has
> to specify those attributes (that is, if Spring does not preserve the
> order).
I would have to look into this, avoiding all this and at the same time
making things more intuitive is my preferred route though.
> > Only allowing the user to configure jmx dependent agents if jmx-server
> > is declared (remember jmx agents locates first, then creates) I
> > believe would be more intuitive and less error-prone for users and
> > also easier for us to manage jmx agents dependencies.
>
> The problem here is if any future agent depends on JMX, the schema has to be
> updated to support it.
Not really. Just add a <management:jmx-custom-agent/> element or
similar, the same we do everywhere else to provide extensibility..
> Not the case if they are top-level.
The same applies top-level there is no difference (at least with 2.0
style configurations). The schema would have jmx-server,
log4j-notification, publish-notification, chainsaw-notifications
agents defined in the schema as elements and a
<management:custom-agent class=""/> for additional or custom agents.
( There is a possibility that Jmx dependent agents implement an
additional interface, and have the MBeanServer set automatically
rather than each of them having to look it up, but this is debatable
and separate to the choice of configuration mechanism.)
Maybe I should get together the schema for what I suggest to better
see what I mean?
Also be interesting to know what the other 2.0 guys think...
Dan
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: Mule Agents 2.0 Configuration
| Free embeddable forum powered by Nabble | Forum Help |
