[ http://issues.apache.org/jira/browse/OJB-82?page=comments#action_12363518 ]
Armin Waibel commented on OJB-82: --------------------------------- A test to reproduce this issue can be found in CollectionTest#testUsingExtentWhichIsNotInheritedFromBaseClass() > Declare 'extent' which is not a subclass or implements interface > ---------------------------------------------------------------- > > Key: OJB-82 > URL: http://issues.apache.org/jira/browse/OJB-82 > Project: OJB > Type: Bug > Components: ODMG-API, PB-API > Versions: 1.0.3 > Reporter: Armin Waibel > > In documentation section 'Extents' the following feature is listed > <snip> > Why is it necessary to explicitely declare which classes implement an > interface and which classes are derived from a baseclass? > ... > In other cases it may be neccessary to treat certain classes as implementors > of an interface or as derived from a base even if they are not. > As an example, you will find that the ClassDescriptor for class > org.apache.ojb.broker.Article in the repository.xml contains an entry > declaring class CdArticle as a derived class: > </snip> > http://db.apache.org/ojb/docu/guides/advanced-technique.html#Extents > Currently this doesn't work because of a workaround in > QueryReferenceBroker#getCollectionByQuery which is used to filter out 'wrong' > objects returned by queries including a "table per class hierarchy" (using > ojbConcreteClass column). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
