two things that I've noticed [1] if during the entities creation, the sequence already exists, openJPA tries to create it again and fails the whole process, so ensure that, on a schema creation failure, no generated tables or sequences are there
[2] starting tomee with 2 web apps, each one using its own resource.xml to define the datasource for the persistence.xml, even if persistence.xml has openjpa.jdbc.schema defined, openjpa still seems to mix things and fails (maybe I should enforce the schema somewhere else), so if I start tomee with one webapp first, it works, and then I can add other webapps one by one and restarting tomee... :-) [] Leo On Wed, Jul 8, 2015 at 12:38 PM, Leonardo K. Shikida <[email protected]> wrote: > Probably the same one I've saw once for dbunit, because schema and users > are the same thing for oracle. > > I think I know what you're talking about. > > Gonna try that > > [] > > Leo > > On Wed, Jul 8, 2015 at 12:28 PM, Romain Manni-Bucau <[email protected] > > wrote: > >> On the phone but can be an issue with schema selection if you have >> multiple >> schema. There is an option to force it. >> Le 8 juil. 2015 08:17, "Leonardo K. Shikida" <[email protected]> a >> écrit : >> >> > oracle 11 (not XE) >> > >> > [] >> > >> > Leo >> > >> > On Wed, Jul 8, 2015 at 12:07 PM, Romain Manni-Bucau < >> [email protected] >> > > >> > wrote: >> > >> > > Hi >> > > >> > > Which database? >> > > Le 8 juil. 2015 07:56, "Leonardo K. Shikida" <[email protected]> a >> > écrit : >> > > >> > > > Hi >> > > > >> > > > is there any known bug related to this? >> > > > >> > > > Sometimes, my web app generates the schema >> > > > >> > > > <property >> > > > name="openjpa.jdbc.SynchronizeMappings" >> > > > value="buildSchema(ForeignKeys=true)" /> >> > > > >> > > > sometimes not. >> > > > >> > > > Some sort of a heinsenbug. :-( >> > > > >> > > > TIA >> > > > >> > > > Leo >> > > > >> > > >> > >> > >
