| Test case for collection handling.
Main class Gatherer have five collections of type CollectibleBase,
CollectibleB, CollectibleC, CollectibleD, CollectibleDD
Class hierarchy:
[CollectibleBaseIF <--] CollectibleBase <-- CollectibleB <-- CollectibleC <-- CollectibleCC
| |
CollectibleD <-- CollectibleDD CollectibleCCC
in repository interface CollectibleBaseIF was declared with five
extents (CollectibleBase, CollectibleB, CollectibleC, CollectibleD, CollectibleDD)
CollectibleBase
auto-retrieve, auto-update, auto-delete all true
proxy false
CollectibleB
auto-retrieve, auto-update set true, auto-delete false
proxy true
CollectibleC
auto-retrieve, auto-update, auto-delete set true,
proxy true
CollectibleC has a reference back to the Gatherer object
(auto-retrieve, auto-update, auto-delete set false to avoid circular
object creation)
CollectibleCC
auto-retrieve true, auto-update true, auto-delete set true,
proxy false
CollectibleCCC
auto-retrieve false, auto-update true, auto-delete set true,
proxy false
CollectibleD
auto-retrieve, auto-update, auto-delete all true
proxy false
CollectibleDD
auto-retrieve, auto-update, auto-delete all true
proxy true
TODO: Need some refactoring and more structured tests of different auto_xyz/proxy settings
author: Armin Waibel version: $Id: CollectionTest.java,v 1.11.2.7 2005/12/29 22:18:21 arminw Exp $ |