[
https://issues.apache.org/jira/browse/ISIS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood updated ISIS-2018:
------------------------------
Description:
Add in some checks to ensure that the two caches within
SpecificationCacheDefault never get out of step.
Needs to take into account / improve the horrible kludge of the ThreadLocal
used in calls around invalidateCache, in
ObjectSpecificationAbstract#getAssociation(String id)
~~~
Also, probably don't need to eagerly introspect all specs. Perhaps just enough
to determine the ObjectSpecId. Should there be three levels of introspection?
NOT_INTROSPECTED, OBJECT_SPEC_ID_INTROSPECTED, FULLY_INTROSPECTED ?
was:
Add in some checks to ensure that the two caches within
SpecificationCacheDefault never get out of step.
Needs to take into account / improve the horrible kludge of the ThreadLocal
used in calls around invalidateCache, in
ObjectSpecificationAbstract#getAssociation(String id)
> Improve spec cache management
> -----------------------------
>
> Key: ISIS-2018
> URL: https://issues.apache.org/jira/browse/ISIS-2018
> Project: Isis
> Issue Type: Improvement
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Major
> Fix For: 2.0.0-M2
>
>
> Add in some checks to ensure that the two caches within
> SpecificationCacheDefault never get out of step.
> Needs to take into account / improve the horrible kludge of the ThreadLocal
> used in calls around invalidateCache, in
> ObjectSpecificationAbstract#getAssociation(String id)
> ~~~
> Also, probably don't need to eagerly introspect all specs. Perhaps just
> enough to determine the ObjectSpecId. Should there be three levels of
> introspection? NOT_INTROSPECTED, OBJECT_SPEC_ID_INTROSPECTED,
> FULLY_INTROSPECTED ?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
