"OJB Users List" <[EMAIL PROTECTED]> schrieb am 27.02.04 16:41:44: > > On Fri, 27 Feb 2004, Kim Wegerle wrote: > > > I changed the JDBC driver, the protocol, the suprotocol, the db alias, the > > sequence manager and the sequence used in the repository. I created an equal db > > scheme in oracle. I setup the odmg internal tables. After that it was possible to > > use the web application like on mySQL, except those exceptions while inserting, > > deleting and updating. > > I first thought you migrated within a running OJB app (e.g. dynamic > switching between connection descriptors). Well, AFAIK OJB Proxies are not > database dependent so your error is definitly strange. There are a > two things that you might want to try : > > * test this with the CVS version of OJB > * disable some/all proxies to see whether it is working at all with Oracle > (it might be some strange sequence + collection-class + proxy bug) > > Also, can you get a complete stacktrace (it currently ends at > storeCollectionObject) ? (the more information the better ;-) ) > > I'm no expert on the Oracle implementation, so if you get nowhere with the > above, I'm sure it would help a lot if you could condense your problem > into a test case against OJB ... > > Regards, > Tom > > Ok, I've found the problem. There have been some missing refresh="false" attributes in some associations. I also changed all autos(auto-delete="false" auto-retrieve="true" auto-update="false"). Now it works fine :-) Thanks for your help :-D
Best regards Kim Wegerle ______________________________________________________________________________ Nachrichten, Musik und Spiele schnell und einfach per Quickstart im WEB.DE Screensaver - Gratis downloaden: http://screensaver.web.de/?mc=021110 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
