B�rries Ludwig wrote: > > Hi Bruce, > > unfortunatly my example does not work at all, although it should be the > simple self-referenced n:m-mapping in your opinion. It would be great if you > could send me an example for a simple self-referenced n:m-mapping that works > :-) >
Borries, I've only experienced simple one-to-one self relations to work. I've never seen simple many-to-many self relations work, nor do I think it's possible in Castor JDO. This is what I meant when I said that your example demonstrated that even simple self relations break down rather quickly (i.e. they just do not work with Cator JDO). Because you've chosen Castor JDO for your project, I would recommend changes in the design of your object model and/or relational model to make up for the lack of self relational support. BTW, because of the lack of self relations (and some other things) I've investigated many commercial object persistence products and some do support self relations. Off the top of my head, I can only remember that TopLink does support this and that Cocobase does not (as of the time of my investigation back in June). The real catch with something like TopLink is that there development as well as a deployment costs. Here is a link to a page listing many other products providing object persistence and/or XML data binding. In fact, this page has many more items since I last viewed it back in June: http://www.javaskyline.com/database.html -- +------------------------------+ | Bruce Snyder | | [EMAIL PROTECTED] | +------------------------------+ ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [EMAIL PROTECTED] with a subject of: unsubscribe castor-dev
