Re: Non decomposed problem

For M:N mappings, you should not use auto-delete (that will remove the M or N side - depending on config/code). You should use 'auto-delete=false' and a 'collection-class=org.apache.ojb.broker.util.RemovalAwareCollection' (I don't remember the complete class name - please, double check it). This

Multiple table entries on vector object.

I have a 1:m setup with a vector of objects. When the data is saved to the database there's double entries showing in the database table. To explain further in case I'm not clear. I have an object with a vector of college objects in it. I add several college objects to the vector in the app

reference-descriptor ???? help ???? urgent

Hi all How map the reference-descriptor correctly i have the following : class-descriptor class=br.com.fernandoqueiroz.sgbd.negocio.Cidade table=C_TCIDADE field-descriptor name=id_cidade column=id_cidade jdbc-type=INTEGER primarykey=true autoincrement=true/ field-descriptor

Re: reference-descriptor ???? help ???? urgent

Just use the auto-retrieve=true auto-update=true auto-delete=true. http://db.apache.org/ojb/tutorial3.html#Setting%20Load,%20Update,%20and%20Delete%20Cascading Go here. Justin A. Stanczak Web Manager Shake Learning Resource Center Vincennes University (812)888-5813 Please turn your

Re: Non decomposed problem

Hi And thanks for this PB tips! But it doesn't seems to work with odmg, in fact I saw ( comment in source ) that RemovalAwareCollection are there to be used with PB This will allow to use the PB api in way pretty close to ODMG persistent collections! ( dixit Thomas Mahler ).

Re: [OTM] can not delete from dependent collection

Hi Joerg, I think I have solved all the problems that you mentioned, and even more ;-) I confirm that otm-dependent=true must be used with auto-update=false. Thank you very must for the ideal bug report! :-) Regards, Oleg On Tuesday 24 February 2004 17:45, Joerg Heinicke wrote: Hello, I'm

Re: Multiple table entries on vector object.

Hi Justin, anyone's guess ... ;-), did you set auto-update 'true' in your collection-descriptor? If set true you will get double inserts. When using the odmg-api it's not allowed to set auto-update/auto-delete 'true'. regards, Armin [EMAIL PROTECTED] wrote: I have a 1:m setup with a vector of

Help needed with xdoclet- many thanks

Thomas Thank you very much for your in depth reply. Much appreciated. I knew it was something really silly that I was not doing properly. I had to change the directory structure to include the package path. All is working fine now. Thanks also for writing this tool. It certainly is very

success deploying ojb in jboss

Thanks Andrew and Armin. I followed Andrew's advice and packaged everything in one ear. Good news is I am also able to redeploy without having to restart the app-server (no OJB redeployment issues so far). Here's how I did it: /ejb.jar/ ...EJBs ...DAOs ...META-INF/ ..ejb-jar.xml

using single persistence broker instance

I was wondering if anyone out there could comment on my usage of PersistenceBroker in an EJB. I currently create a single instance during ejbCreate and keep it for the duration of the bean's lifecycle. This seems like the most efficient way. Is there a danger to using this approach when