[
https://issues.apache.org/jira/browse/CONFIGURATION-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12702857#action_12702857
]
Ralph Goers commented on CONFIGURATION-203:
-------------------------------------------
With regards to the situations you mentioned I would strongly argue that there
are much better solutions than serializing the whole configuration. Especially
in the case of the EJB, in a properly designed system the client side and the
server side would usually have completely different configuration data so
passing the full set of configuration would be a waste. Furthermore, passing
the data would hardly be better than having the server side just read its
configuration.
If we assume that the configuration itself wouldn't be Serializable, as we both
seem to agree, then storing something else in the session isn't of much value
since you would have to keep reconstructing the Configuration to actually
access the data. If you really wanted to do this it would make much more sense
to just add save(OutputStream) to the base Configuration interface. Then the
application could save any configuration to a byte array and load it back in
again later. As for the end user data in the session, that really should be
some sort of UserPreferences object, not a serialized configuration object. The
UserPreferences object could certainly be backed by a Configuration, but once
the object is built the Configuration would never be needed again in that
session unless the user changes a setting.
I have no problem setting this to 2.0. I am just stating my doubts that
anything will ever happen with this issue.
> 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.
