[
https://issues.apache.org/jira/browse/CONFIGURATION-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702713#action_12702713
]
Oliver Heger commented on CONFIGURATION-203:
--------------------------------------------
Serializing a Configuration only to make it persistent certainly does not make
much sense. But the other use cases listed in this ticket seem valid to me.
Consider a web application that creates a Configuration with settings for a
user on log in. This Configuration should be stored in the Session, so it
should be serializable. It may also be used as a parameter of a call to a
remote EJB, which also requires it to be serializable.
But as I said, I don't believe that we can make concrete Configuration
implementations themselves serializable, only the pure data they contain. In
the case of combined configurations that would mean creating a serializable
data object containing the data of all child configurations involved.
Anyway, I agree that this issue will probably not be addressed in the 1.x
series. So I am going to change the fix version.
> 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.
-
You can reply to this email to add a comment to the issue online.
