You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Kevin Sutter (JIRA)" <ji...@apache.org> on 2009/12/23 16:34:29 UTC
[jira] Created: (OPENJPA-1446) @DataCache and @Cacheable not
extending to subclasses
@DataCache and @Cacheable not extending to subclasses
-----------------------------------------------------
Key: OPENJPA-1446
URL: https://issues.apache.org/jira/browse/OPENJPA-1446
Project: OpenJPA
Issue Type: Sub-task
Components: datacache
Affects Versions: 2.0.0-M3
Reporter: Kevin Sutter
While working through issues with the caching testcases enabled for the parent JIRA (openjpa-1443), I discovered that the @DataCache(false) setting was not getting applied to subclasses in the hierarchy. This annotation is supposed to indicate that this Entity should not be cached. One of the tests in CacheTest.testCacheNames is attempting to verify that this annotation is also applied to any child classes. Unfortunately, this doesn't look to be working correctly. So, I temporarily commented out that specific test...
// assertCacheName(CacheObjectBChild1.class, null);// sub-classes should inherit parent's @Cacheable setting
I couldn't find anywhere in our documentation that @DataCache should apply to child Entities or not. But, since this capability is also part of the JPA 2.0 specification via the @Cacheable annotation, I figured that we should follow suit. I also checked out suite of tests for the @Cacheable annotation and we don't seem to be testing the inheritance of this flag either. So, it looks like we need to resolve this both for @DataCache and @Cacheable, fix up or add more tests, and update the documentation accordingly.
Thanks,
Kevin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-1446) @DataCache and @Cacheable not
extending to subclasses
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar updated OPENJPA-1446:
-----------------------------------
Comment: was deleted
(was: I am on vacation from 12/20/2009 Â to 12/26/2009.
If you have any question on deployment and JEE bugs, please contact Saurabh Arora or my manager Maruthi Nuthikattu.
For emergency, contact me at 925-209-5517.
)
> @DataCache and @Cacheable not extending to subclasses
> -----------------------------------------------------
>
> Key: OPENJPA-1446
> URL: https://issues.apache.org/jira/browse/OPENJPA-1446
> Project: OpenJPA
> Issue Type: Sub-task
> Components: datacache
> Affects Versions: 2.0.0-M3
> Reporter: Kevin Sutter
>
> While working through issues with the caching testcases enabled for the parent JIRA (openjpa-1443), I discovered that the @DataCache(false) setting was not getting applied to subclasses in the hierarchy. This annotation is supposed to indicate that this Entity should not be cached. One of the tests in CacheTest.testCacheNames is attempting to verify that this annotation is also applied to any child classes. Unfortunately, this doesn't look to be working correctly. So, I temporarily commented out that specific test...
> // assertCacheName(CacheObjectBChild1.class, null);// sub-classes should inherit parent's @Cacheable setting
> I couldn't find anywhere in our documentation that @DataCache should apply to child Entities or not. But, since this capability is also part of the JPA 2.0 specification via the @Cacheable annotation, I figured that we should follow suit. I also checked out suite of tests for the @Cacheable annotation and we don't seem to be testing the inheritance of this flag either. So, it looks like we need to resolve this both for @DataCache and @Cacheable, fix up or add more tests, and update the documentation accordingly.
> Thanks,
> Kevin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-1446) @DataCache and @Cacheable not
extending to subclasses
Posted by "Xiaoqin Feng (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794874#action_12794874 ]
Xiaoqin Feng commented on OPENJPA-1446:
---------------------------------------
I am on vacation from 12/20/2009 Â to 12/26/2009.
If you have any question on deployment and JEE bugs, please contact Saurabh Arora or my manager Maruthi Nuthikattu.
For emergency, contact me at 925-209-5517.
> @DataCache and @Cacheable not extending to subclasses
> -----------------------------------------------------
>
> Key: OPENJPA-1446
> URL: https://issues.apache.org/jira/browse/OPENJPA-1446
> Project: OpenJPA
> Issue Type: Sub-task
> Components: datacache
> Affects Versions: 2.0.0-M3
> Reporter: Kevin Sutter
>
> While working through issues with the caching testcases enabled for the parent JIRA (openjpa-1443), I discovered that the @DataCache(false) setting was not getting applied to subclasses in the hierarchy. This annotation is supposed to indicate that this Entity should not be cached. One of the tests in CacheTest.testCacheNames is attempting to verify that this annotation is also applied to any child classes. Unfortunately, this doesn't look to be working correctly. So, I temporarily commented out that specific test...
> // assertCacheName(CacheObjectBChild1.class, null);// sub-classes should inherit parent's @Cacheable setting
> I couldn't find anywhere in our documentation that @DataCache should apply to child Entities or not. But, since this capability is also part of the JPA 2.0 specification via the @Cacheable annotation, I figured that we should follow suit. I also checked out suite of tests for the @Cacheable annotation and we don't seem to be testing the inheritance of this flag either. So, it looks like we need to resolve this both for @DataCache and @Cacheable, fix up or add more tests, and update the documentation accordingly.
> Thanks,
> Kevin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.