You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2013/03/16 16:02:14 UTC

[jira] [Commented] (CONFIGURATION-203) Make Configuration Serializable

    [ https://issues.apache.org/jira/browse/CONFIGURATION-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604289#comment-13604289 ] 

Oliver Heger commented on CONFIGURATION-203:
--------------------------------------------

In times of CDI, wouldn't it be possible to write an extension which loads a configuration and injects it into interested beans based on annotation? Or even inject only specific configuration property values? This approach allows using configuration objects in a JEE environment without requiring that they have to be serializable. Maybe something for the DeltaSpike project?
                
> Make Configuration Serializable
> -------------------------------
>
>                 Key: CONFIGURATION-203
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-203
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.1
>            Reporter: Joe Wolf
>            Priority: Minor
>             Fix For: 2.0
>
>
> It would be nice if org.apache.commons.configuration.Configuration extended java.io.Serializable and its implementations were serializable as well.  Theoretically, most configurations are constructed from "serialized" data sources.

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