[jboss-jira] [JBoss JIRA] (AS7-6345) <vault> does not have module option

Thu Apr 18 13:36:53 EDT 2013

    [ https://issues.jboss.org/browse/AS7-6345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768567#comment-12768567 ] 

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/jboss/as/logging/HandlerOperations.java#L186
https://github.com/jbossas/jboss-as/blob/master/logging/src/main/java/org/jboss/as/logging/HandlerOperations.java#L233

> <vault> does not have module option
> -----------------------------------
>
>                 Key: AS7-6345
>                 URL: https://issues.jboss.org/browse/AS7-6345
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Security
>    Affects Versions: 7.1.3.Final (EAP)
>            Reporter: James Livingston
>            Assignee: Peter Skopek
>
> The <vault> element in standalone/domain.xml takes a 'code' attribute specifying the class to use as the implementation. It does not let you specify a 'module' option like most similar elements have, and instead always loads the class from the org.picketbox module.
> The <vault> element should take a module option too.

--
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