Yes, I remember Use Case constructs of Xcalia. What was appealing about Use Case concept is that it is not only a powerful construct but also practical -- it is a neat way to separate development (business logic etc) versus deployment concerns (database performance etc.) in a design.
OpenJPA FetchConfiguration (the original kernel constructs that appear as FetchPlan on JPA facade) is quite similar to Use Case. In fact, beside access path a FetchConfiguration carries the locking modes as well. Moreover, many critical mechanics (push/pop them on contexts, effective state cloning for multithreaded usage or traversal, meta-data/annotation based configuration) are built on the FetchConfiguration structure and also it is uniformly available to all critical operations within the kernel. So one can effectively augment the structure with more details without perturbing the internal API. Slice (the multi-tenancy module), FetchConfiguration is augmented to target queries to specific shards, for example, without breaking the API on top. ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/OpenJPA-rock-and-fetch-plan-is-a-killing-feature-tp5978322p5982760.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
