Bug 901327 (JBPAPP6-1795)

Summary: <vault> does not have module option
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: James Livingston <jlivings>
Component: SecurityAssignee: Peter Skopek <pskopek>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: anmiller, jawilson, jcacek, jdoyle, jlivings, joallen, myarboro, sappleto, tfonteyn
Target Milestone: ---   
Target Release: EAP 6.3.0   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBPAPP6-1795
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-23 06:10:59 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Livingston 2013-01-17 00:13:44 UTC 
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A000000CReKQ&sfdc.override=1
project_key: JBPAPP6

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.
Comment 1 James Livingston 2013-01-17 00:14:51 UTC 
Link: Added: This issue incorporates AS7-6345
Comment 8 JBoss JIRA Server 2014-03-17 21:41:19 UTC 
Kabir Khan <kabir.khan> updated the status of jira WFLY-922 to Resolved
Comment 9 JBoss JIRA Server 2014-03-29 17:12:32 UTC 
Kabir Khan <kabir.khan> updated the status of jira WFLY-3118 to Closed
Comment 10 Jimmy Wilson 2015-04-23 06:10:59 UTC 
This was resolved in EAP 6.3.  I'm closing this BZ.
Comment 11 JBoss JIRA Server 2015-04-28 15:09:31 UTC 
John Doyle <jdoyle> updated the status of jira EAP6-190 to Closed