I have configured
Castor to support a many-to-many relationship between two types of objects, but
I'm getting an error. This is because the mapping table itself (in Oracle)
contains a primary key of its own, and this is not automatically assigned by
Castor. So when a new relationship is created, this primary key is null
and the database throws an error.
I don't have control
over the database schema - is there any way to configure Castor to recognize
that the configured many-table has a primary key and the key can be created
using the sequence key generator? (the sequence key generator
works fine for everything else) Or am I going to be forced to create
a "map" object that handles the relationship 'manually'?
-Ron
