I will look at it.
I have finished to integrate it, thank you Timothy, this is your second module (first was quote).
I had to modify nukes to make it works. Now the JDBCDeploymentScanner reacts better to class loading/unloading.
When a class is undeployed, the scanner remove the deployments (you were doing that explicitely in your module). If you read the classes later it will redeploy the waiting module.
I modified the polls block name, instead of having nukes.blocks:name=poll2, I modified to take advantage of JMX key properties in the name : nukes.blocks:name=poll,id=2. The poll block takes its ID in the preRegister method.
I removed the JMX listener stuff, a good trick but a bit twisted. So, the module still deploys the blocks but if the user want to configure them he will use the JMX module or the block module instead.
Again, thank you, if you need CVS access to modify your work or add some other, you are welcome.
Thanks for taking the time to integrate my code. I get alot out of your comments, and also looking at the code changes you make.