Skip to content
This repository has been archived by the owner on Jul 24, 2019. It is now read-only.

Custom / long term serialization support for StateHolder API #42

Closed
mysticfall opened this issue Feb 12, 2013 · 1 comment
Closed

Custom / long term serialization support for StateHolder API #42

mysticfall opened this issue Feb 12, 2013 · 1 comment
Assignees
Milestone

Comments

@mysticfall
Copy link
Owner

Need a custom serialization support for StateHolder API to support long term persistence of the model state (i.e. saving as a file for the Pentaho platform).

@mysticfall
Copy link
Owner Author

On second thought, I don't think we should use StateHolder API for long term persistence at all. The main usage for the API was to provide short term state management in such a case as session state needs to be serialized.

For the long term persistence, or externalization I don't think it should store model's internal state like ExpNode tree like the StateHolder API does.

Instead, I think the externalization process only relies on the public properties of the model and renderer instance, which can be easily implemented according to each project's needs.

@mysticfall mysticfall reopened this Feb 23, 2013
mysticfall pushed a commit that referenced this issue Feb 23, 2013
- Add the commons-configuration library dependency.
- Refactoring on package names.
@ghost ghost assigned mysticfall Feb 23, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant