> This is not a generic solution. It's simply a work around for a special case.
>Besides it
> only allows a once off configuration, what if I later want to add another
>configuration
> ? It might be sufficient for this one simple case, but not much more.
>
The jboss.jcml file is a read once mechanism that is used by the ConfigurationService
mbean to an initialized state with respect to the jboss.jcml specified attributes. It
also
defines a simple linear dependency mechanism which translates into the order in which
the ServiceControl mbean invokes the init/start/stop/destroy lifecycle methods.
> JMX defines (I think I'm right in saying) attributes which map via a getter/setter
> pattern onto a Bean property and are supported by jboss.jcml and operations, which
>seem
> to be all methods which do not fit the attribute pattern.
>
> Why not simply allow the calling of these operations (albeit just the ones that take
>0-N
> String args) via jboss.jcml.
>
This is not a simple change to the current ConfigurationService/ServiceControl mbeans.
In
general an mbean operation cannot be invoked until the mbean's prequisite mbeans are
available.
> At the moment I am just using a Configuration attribute, and can call
>setConfiguration
> multiple times to achieve the effect that I want, but the semantics are all wrong. My
> configuration is not an attribute.
>
Configuration appears to be an array attribute that can be modified via
addConfiguration/removeConfiguration operations in addition to the standard
JavaBean style setters. The use case your describing does not require the ability
to define operation invocations in jboss.jcml.
> There must be other MBeans out there which have an interface which is not solely
> comprised of attributes. Does no-one need access to other operations on their MBeans
>?
>
Many of the bundled mbeans have operations in addition to attributes, but the
operations
typically cannot be invoked until the mbean has reached a started state.
You seem to be looking for an ability to bring a JBoss server to an arbitrary state ala
xml scripting which is fine, but it is a significant enchancement over the current
mbean
service notion. This is along the lines of the XMLet Stacy Curl has done some work
on that allowed for arbitrary operations to be invoked at each point in the logical
init/start/stop/destroy lifecyle of an mbean. Can this be developed into a drop in
replacement for the current mbean service initialization mechanism?
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
