I have verified this failure - and it is not just ODMG, but it is a particular problem of an Extent that contains only one class, and that class has an ojbConcreteClass attribute.
This may sound like an odd situation, but it could happen if you have an interface mapped to just one OJB concrete class, and it happened to me during testing, as I have 2 classes mapped to one table, but there is an interface that only maps to one of them. I have written a test for the problem, found, and corrected the problem in my working copy. I have posted an issue to scarab http://scarab.werken.com/scarab/issues/id/OJB114 and I will supply a patch as soon as OJB CVS is available again (apparently OJB CVS is down right now? Russell On Thu, 2002-12-05 at 16:50, J. Russell Smyth wrote: > It appears to me that extents do not work correctly when using ODMG and > multiple classes on a single table. I have a configuratation that works > fine untill I add the ojbConcreteClass field descriptor > > <field-descriptor > id="5" > name="ojbConcreteClass" > column="CLASS_NAME" > jdbc-type="VARCHAR" > nullable="true" > > /> > > After I add this I can no longer query (using OQL) the extent. > > Can anyone verify that they have this working(or not)? > > Thanks > Russell > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
