[jira] [Created] (ISIS-2018) Improve spec cache management

[Dan Haywood (JIRA)]

Dan Haywood created ISIS-2018:
---------------------------------

Summary: Improve spec cache management
Key: ISIS-2018
URL: https://issues.apache.org/jira/browse/ISIS-2018
Project: Isis
Issue Type: Improvement
Reporter: Dan Haywood
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)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[Dan Haywood (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood reassigned ISIS-2018:
---------------------------------

Assignee: Dan Haywood

Post by Dan Haywood (JIRA)
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)

--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[Dan Haywood (JIRA)]

[ 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)

Post by Dan Haywood (JIRA)
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)

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661037#comment-16661037 ]

ASF subversion and git services commented on ISIS-2018:
-------------------------------------------------------

Commit 34007526f666e01232efee12b389358f63646861 in isis's branch refs/heads/ISIS-2018 from danhaywood
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3400752 ]

ISIS-2018: adds in guards around SpecificationCacheDefault (disabled for now).

Post by Dan Haywood (JIRA)
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)