[ https://issues.jboss.org/browse/AS7-6345?page=com.atlassian.jira.plugin.s... ] Brian Stansberry commented on AS7-6345: --------------------------------------- It's a borderline bug, since providing a plugin point that requires the user to modify the module.xml for an internal module in order to allow the plugin to be loaded is basically broken. The coding magic is pretty simple; you read the name of the module from the new "module" attribute and if defined get the module and use its classloader to load the class specified by the "code" attribute. See, for example: https://github.com/jbossas/jboss-as/blob/master/logging/src/main/java/org... https://github.com/jbossas/jboss-as/blob/master/logging/src/main/java/org... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira