What AS5 instance are you running? Did you check the HackCLMDD code? There are (currently) two usages. 1) there is LoaderRepositoryConfig present in attachments 2) we're not top level deployment unit, and there is parent CLMD present
This deployer is always triggered. And all it does - applying the 2 rules from above - is add ClassLoaderMetaData. This CLMD is later picked by ClassLoaderDeployer (if it exists). Regarding 'console-mgr.sar', I guess this is the only deployment that has strict scoping defined, hence the LoaderRepositoryConfig being present. | <loader-repository> | jboss.console:sar=console-mgr.sar | <loader-repository-config> | java2ParentDelegation=true | </loader-repository-config> | </loader-repository> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4126279#4126279 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4126279 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
