[jboss-jira] [JBoss JIRA] (WFCORE-3877) Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components.

[Jeff Mesnil (JIRA)]

     [ https://issues.jboss.org/browse/WFCORE-3877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil updated WFCORE-3877:
--------------------------------
    Fix Version/s: 6.0.0.Alpha5
                       (was: 6.0.0.Alpha4)


> Make implementing the org.wildfly.extension.elytron.Configurable optional for configurable components.
> ------------------------------------------------------------------------------------------------------
>
>                 Key: WFCORE-3877
>                 URL: https://issues.jboss.org/browse/WFCORE-3877
>             Project: WildFly Core
>          Issue Type: Feature Request
>          Components: Security
>            Reporter: Darran Lofthouse
>            Assignee: Martin Mazanek
>             Fix For: 6.0.0.Alpha5
>
>
> Presently custom components within the Elytron subsystem are required to implement the 'org.wildfly.extension.elytron.Configurable' interface if they wish to support receiving a Map of configuration Strings.  
> This means that the custom component needs to depend on both the WildFly Elytron project and the subsystem.
> It should be possible for components to add the following method without implementing the interface and be configurable.
> {noformat}
> void initialize(final Map<String, String> configuration);
> {noformat}
> We also have a long standing issue in that if we add a new component to WildFly Elytron it can not be used until we can add a resource to configure it.  By supporting configurable custom components without needing a dependency on the subsystem new components added to WildFly Elytron could be usable whilst the subsystem definitions catch up.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)