Peter,
I ended up making listeners deployed from assembly.xml and can include configuration from config.xml like blocks. Any objections?Sounds really cool. No objections here.....but have you though about future needs for permissions IRO this, i.e. does the assembler grant the right to listen to one or more blocks for changes, or ir it enough for the Java code to implement BlockListener for all to become apparent to them?
Hmmm, just digging a bit deeper, I've seen more of what you've done (always more polite to look rather than guess ;-)
From assembly.xml :
<block-listener class="org.apache.avalon.cornerstone.demos.simpleserver.SimpleBlockListener" name="simple-listener" />
This looks to be indicating that it will listen to all blocks being added,changed & deleted. If we need some pattern based filtering of blocks, we can do it there .. another-day(tm).
Is there suppot for multiple block listeners per sar? Though they are distributed in bar files, can they a) be blocks too or b) have interaction with blocks? People might resort to static stuff to make interactions possible.... :-(
Regards,
- Paul H
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
