[jboss-jira] [JBoss JIRA] (ELY-837) Clean up provider usage and definition in XML config

[Darran Lofthouse (JIRA)]

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

Darran Lofthouse commented on ELY-837:
--------------------------------------

ELY-840 starts to make it possible to use Providers discovered later within the configuration, this should be extended to provider discovery is at the metaphorical root of configuration and then children can have a provider-name attribute to filter by name.

> Clean up provider usage and definition in XML config
> ----------------------------------------------------
>
>                 Key: ELY-837
>                 URL: https://issues.jboss.org/browse/ELY-837
>             Project: WildFly Elytron
>          Issue Type: Task
>          Components: XML
>            Reporter: David Lloyd
>            Priority: Critical
>
> We are very inconsistent about how we're defining and using providers in the XML configuration.  We need to meet the following requirements:
> * Provide a single top-level element from the substitution group {{abstract-providers}} that specifies the providers to use in the absence of any other configuration; default to {{use-system-providers}}
> * Update the following types (or appropriate enclosing type) to accept an optional nested {{abstract-providers}} override:
> ** {{key-store-type}}
> ** {{credential-store-type}}
> ** {{hashed-password-type}}
> * Update the following types to use an optional {{provider}} *attribute* (not nested element) to allow selection of a specific provider:
> ** {{credential-store-type}}
> ** {{key-store-type}} -- already done!
> ** {{hashed-password-type}}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)