Cl�vis Wichoski wrote:
If I use a reference with super keyword in a subclass, and determine-extents="false" in super-class and include-inherited="false" in subclasses, all fields from super classes are recognized in Query of subclasses, but for collections don't ie: (FROM Company WHERE shortcut = "COMPANYX" works but FROM Company WHERE myAddress.myCity.name = "CITYX" don't), because what OJB don't investigate superclass descriptor about collections and references to resolve query path expressions? There are any design issues about this? this is done for fields but don't for collections.
As I said, there are some issues with querying when using the multiple-joined-tables strategy. Could you perhaps add a bug to Scarab for this ?
ok, I understand all of this, but the idea of ojb-check-colletions-from-super, is to reduce errors from changes in super, think this, you had a super class that have 20 subclasses, if you add only one new field in this superclass then you need to change all subclasses with a include-inherited part for this new field.
This is a design choice because I wanted to make the javadoc-'api' as simple as possible (few, easy-to-understand tags) without sacrificing flexibility. And in that regard, the ability to ignore inherited features for one given class without affecting its base- or subclasses is IMO the easiest way. And cases with 20 subclasses that all ignore or change several baseclass features is somewhat rare, I think.
Tom
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
