you need to place the block-service.xml file in the nukes.last directory so it is deployed after the module. or you have to package the block-service.xml file inside the sar so it deploys w/ the classes.
if you hot deploy the module again, you're going to have to touch the -service.xml file again to get it to reload. altho - now that i think about it, you could probably hook into the block's mbean and force a restart when the module is redeployed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3841364#3841364 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3841364 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
