Re: [castor-dev] New child objects in m:n relation not created in Persistent storage when creating new parent

[Bert van Brakel]

Sorry, I've tried that but it doesn't work.   If the permission  id is null castor throws an error, if I set the id to a empty string it creates the child objects with correct generated ids, but there is only one relation in the role_permission_map table (correct role id, empty string permission id).   If I set the permission ids (unique)  before adding them to the role, the role_permission_map contains two relations between the role and the permissions using the correct role id, and the original permission ids (the ones I set). But the permissions table contains the permissions with autogenerated ids (different from the ones i had given the permissions).   So, in the end I still have to create the permissions using db.create( permission ).   Bert. ----- Original Message ----- From: Thomas Yip To: [EMAIL PROTECTED] Sent: Friday, January 18, 2002 8:52 AM Subject: Re: [castor-dev] New child objects in m:n relation not created in Persistent storage when creating new parent   Have you try to setAutoStore( true )? It will create reachable independent object automatically. Remember to call it before you start the transaction     Thomas     -----Original Message----- >From: Bert van Brakel [mailto:[EMAIL PROTECTED]] >Sent: Thursday, January 17, 2002 2:11 AM >To: [EMAIL PROTECTED] >Subject: Re: [castor-dev] New child objects in m:n relation not created in Persistent storage when creating new parent > >Unfortunately I think so too. Permissions are seperate entities in storage. I want them created automatically, but not deleted. I can't make permissions dependent for that reason. >  >Oh well, I'll have to live with it then, unless anyone else has any bright ideas. >  >Bert >----- Original Message ----- >>From: Christopher Sturm >>To: [EMAIL PROTECTED] >>Sent: Thursday, January 17, 2002 2:16 PM >>Subject: Re: [castor-dev] New child objects in m:n relation not created in Persistent storage when creating new parent >> >>I think your Permission class should depend on your Role class in the mapping. >>  >><class name="Permission " identity="id"> >>    <field name="role" type="Role"> >>   </field> >>  </class> >> >>  <class name="Role" identity="id" depends="Permission"> >>      <field name="permission" type="Permission"> >>      </field> >>  </class> >>  >>Otherwise you need to create the Permission objects first and then create your Role. >>-----Original Message----- >>From: Bert van Brakel [mailto:[EMAIL PROTECTED]] >>Sent: Wednesday, January 16, 2002 5:01 PM >>To: [EMAIL PROTECTED] >>Subject: [castor-dev] New child objects in m:n relation not created in Persistent storage when creating new parent >>Why does castor not create new child objects in persistent storage when I create a new parent object? >>  >>Example code: >>    db.begin(); >>    Permission perm1 = new Permission( "perm1" ); >>    Permission perm2 = new Permission( "perm2" ); >>    Role role = new Role(); >>    role.add( perm1 ); >>    role.add( perm2 ); >>    db.create( role ); <------ >>    db.commit(); >>  >>Public methods: >>    The class Permission has get/set Name and Id (String) >>    Role also has get/set Name and Id (String), and get/set Permissions (Collection) >>Relationships: >>    The Permission class is not dependant on Role. >>    There is a m:n relationship between the Role and Permission classes. >>  >>All works OK if I create the permissions first in persistence storage, using a UUID key-genarator (for both Permission and Role), then retrieve the permissions from storage and add them to the role. Mapping between Role and Permission works OK. >>  >>However things don't work fine if I add new permissions to role without first creating them in the persistent storage. Is there a way I can get castor to do this without making  Permissions dependant on Role? >>  >>Maybe castor can't do this yet? >>  >>Any help is much appreciated. >>Thanks, >>Bert. >> >