[
https://issues.apache.org/jira/browse/ISIS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14065625#comment-14065625
]
Jeroen van der Wal commented on ISIS-573:
-----------------------------------------
We currently use (or misuse) @Immutable it disable all members of a class.
Adding caching to the facet would harm the behavior of our applications.
Implementing @Disabled on a class level would provide an alternative for us.
See: ISIS-454
> To improve performance, set up caching of query results against any entities
> that are immutable (ie ref data, ie have ImmutableFacet on them).
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISIS-573
> URL: https://issues.apache.org/jira/browse/ISIS-573
> Project: Isis
> Issue Type: New Feature
> Components: Core, Core: Objectstore: JDO
> Affects Versions: objectstore-jdo-1.1.0, core-1.2.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: core-1.7.0
>
>
> In DN, this is done using:
> query.addExtension("datanucleus.query.results.cached", "true");
> query.addExtension("datanucleus.query.resultCache.validateObjects", "false");
> So, need to figure out how to set up these properties on queries by
> repositories of immutable facets. But this could probably be done
> transparently.
> NB: for these cache results to hang around and not get garbage collected,
> would also need to set the global config parm:
> datanucleus.cache.queryResult.type=strong
> ... its default value is weak.
> Further info at:
> http://www.datanucleus.org/products/datanucleus/jdo/query_cache.html#datastoreCompilation
--
This message was sent by Atlassian JIRA
(v6.2#6252)
