Hello, I found a bug in org.apache.ojb.broker.core.CollectionTypes#getCollectionClass(Collection Descriptor). The "isAssignableFrom" check has to be inverted. For instance: HashSet.class.isAssignableFrom(Set.class) yields false and a MetadataException is thrown. Inverted to Set.class.isAssignableFrom(HashSet.class) yields true and the correct branch gets entered.
Another bug is in the statement creation when a subclass is involved. Note: A0 is the subclass table from A1, PHB_USRID exists only in A1 1.0.4 creates something like SELECT A0.PHB_ID , A1.PHB_USRID , FROM IPT_PHONEBOOKCSV A0 INNER JOIN IPT_PHONEBOOK A1 ON A0.PHB_ID = A1.PHB_ID WHERE PHB_USRID IS NULL 1.0.5rc1 creates SELECT A0.PHB_ID , A1.PHB_ID , A1.PHB_USRID , FROM IPT_PHONEBOOKCSV A0 INNER JOIN IPT_PHONEBOOK A1 ON A0.PHB_ID = A1.PHB_ID WHERE A0.PHB_USRID IS NULL The WHERE criteria assignment to A0 the statement produces an exception for the nonexisting column A0.PHB_USRID. Note, that in the SELECT of 1.0.5rc1 is also A1.PHB_ID, which is not in the statement of 1.0.4. Regards, Sascha Broich --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]