Enable read of cache.default_expiration from NH configuration
Description
Environment
None
Activity
Show:
Fixed
Details
Details
Assignee
Unassigned
UnassignedReporter
Fabio MauloComponents
Fix versions
Affects versions
Priority
MajorWho's Looking?
Open Who's Looking?
Created May 29, 2009 at 8:47 PM
Updated July 30, 2011 at 2:05 PM
Resolved May 29, 2009 at 9:54 PM
Who's Looking?
In the 1.2.0 version the NH conf. properties was not checked by XSD.
During the implementation of the new configuration we had lost the "expiration".
We should continue the support of "expiration" to avoid breaking change and we must support the new property "cache.default_expiration".
All cache providers.