hello,
we start working on this issue. Hope till next release this will be fixed.
thank you for the info!
I really was searching long and was not able to find any information about that, so I'm glad to hear any response from you.
The issue is noted in the release-notes:
<snip>
- When a class mapped on multiple joined tables was used in a reference only objects
of the base type class will be instantiated, e.g. a Company class has
a 1:n reference 'employees' to a base class Employee and class Manager extends Employee,
then 'employees' only contains objects of type Employee even if the real type was Manager.
See in OJB test suite ...broker.InheritanceMultipleTableTest#testInheritancedObjectsInCollectionReferences
Same problem occur when query the base class, then OJB only returns objects of base type instead
the real type.
</snip>
But I admit my English is abstruse ;-)
regards, Armin
Thank you, stefan walkner
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
