slow reading email today, sorry (and laptop just crashed hard which was a
bit worrying - no idea why).
anyway, i think people are discussing how extensible we can make schema if
they need to be nested. a lot depends on the kind of nesting. i couldn't
find a good solution for filters which nest aribitrarily (you can define
things like "and-filter" which takes two nested filters for example).
adding at top level is easy - we already have that (connectors). i admit
i *still* don't understand how this works (at the top level).
adding nested is harder (as far as i can tell) - jmx would need a
"managed" element, which other modules would "subclass". so it would look
like:
<mgmt:jmx-server>
....
<foo:managed>
<foo:something/>
<foo:another/>
</foo:managed>
<bar:managed>
<bar:kofrekfoper/>
</bar:managed>
</mgmt:jmx-server>
if that's not sufficient (and there's not something i've missed that makes
this easier than i think, related to the top level inclusion) you could
perhaps express dependencies explicitly:
<mgmt:jmx-server name="jmx"/>
<foo:managed name="bob" dependsOn="jmx"/>
<bar:kodpsako dependsOn="jmx,bob"/>
and then use that to construct a graph, check it doesn't have cycles, and
use it to start things in the correct order (i have some code somewhere
that does this but it's in erlang :o)
andrew
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
