[
https://issues.jboss.org/browse/LOGMGR-189?page=com.atlassian.jira.plugin...
]
James Perkins updated LOGMGR-189:
---------------------------------
Description:
The configuration API should return the instance created via the API. This will allow
LOGMGR-188 to be reverted and simplify how the persisted configuration will be written.
Changes to the object instance will not be reflected in the configuration API. This is
however the desired behavior for properties that should not be written to the
configuration file.
An example use case of this will be for WildFly. A {{SocketHandler}} may be created based
on an {{SSLContext}} configured in Elytron. This handler can be created without the
configuration API and the handler will be set on a {{DelayedHandler}} instance that will
be created via the configuration API.
was:The configuration API should return the instance created via the API. This will
allow LOGMGR-188 to be reverted and simplify how the persisted configuration will be
written.
Allow the instances to be exposed from the configuration API
------------------------------------------------------------
Key: LOGMGR-189
URL:
https://issues.jboss.org/browse/LOGMGR-189
Project: JBoss Log Manager
Issue Type: Feature Request
Reporter: James Perkins
Assignee: James Perkins
The configuration API should return the instance created via the API. This will allow
LOGMGR-188 to be reverted and simplify how the persisted configuration will be written.
Changes to the object instance will not be reflected in the configuration API. This is
however the desired behavior for properties that should not be written to the
configuration file.
An example use case of this will be for WildFly. A {{SocketHandler}} may be created based
on an {{SSLContext}} configured in Elytron. This handler can be created without the
configuration API and the handler will be set on a {{DelayedHandler}} instance that will
be created via the configuration API.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)