[
https://issues.apache.org/jira/browse/VELTOOLS-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claude Brisson resolved VELTOOLS-161.
-------------------------------------
Resolution: Fixed
Fix Version/s: 3.0
all standard tools are now serializable
> allow session toolbox serialization
> -----------------------------------
>
> Key: VELTOOLS-161
> URL: https://issues.apache.org/jira/browse/VELTOOLS-161
> Project: Velocity Tools
> Issue Type: Improvement
> Affects Versions: 2.0
> Environment: all
> Reporter: Claude Brisson
> Priority: Major
> Fix For: 3.0
>
>
> Some session standard tools keep a reference on the Velocity Log, which is
> not serializable.
> Some work is needed to allow session serialization:
> - a short fix is to have those tools keep a transcient reference on the Log
> (and have them check it before each use). Easy to implement, but deserialized
> sessions won't be able to use the logger, unless there is some kind of
> reinitialization mechanism.
> - a proper way to handle this would be to have standard session tools stored
> as transcient objects - the lazy tools initializer will re-create them on
> demand.
> - or maybe the session toolbox itself should be made transcient in the J2EE
> session by means of a little wrapper ; easy to do, but the user may want to
> serialize its own objects.
> I guess the second solution is the more appropriate. Any thought?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
