>> Does DList automatically persist itself in the database on creation?
>
>If you use DListImpl within a tx and you commit tx, then I think the >list will be persist itself. DListImpl_2 does not lock(persist) itself >while a tx is running. You have explicitly lock DListImpl_2 instances >to them persistent in DB.
That explains what I was finding :)
What are the benefits of using DListImpl/DListImpl_2 over a ManageableCollection in ODMG?
>> I tried inheriting TypedSet from DListImpl_2 and got the error as >>below - I'm
>>...
>> Caused by: >>org.apache.ojb.broker.metadata.ClassNotPersistenceCapableException:
>> nz.ac.auckland.markit.core.TypedSet not found in OJB Repository
>> at
>> >>org.apache.ojb.broker.metadata.DescriptorRepository.getDescriptorFor(Unknown >>Source)
>> at
>
>Did you define a class-descriptor for TypedSet in your repository file?
I'm only using TypedSets as collections within persistent classes, so AFAIK i didn't need to in the same way that I don't need to for a plain Collection.
I did try though - i got an error about no primary key (fair enough). How would I go about defining it? declare all the fields but map them to no table? add an id field? use the pbkey or one of the other fields from DLIst as the Primary key?
Thanks for your help,
Rob :)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
