But what I can't ignore is that bug with log4j config that I posted earlier. Especially with a sequence generator. It says that the table is created in HSQLDB database. But manual investigation shows no such table. But when generator is forced to re-create the (theoretically) existing sequence related table - it says that table is existing(?!). So I need help with that log4j bug to figure out what is happening. Looks like that it is sequence generator related bug. John
2010/5/17 Michael Dick <michael.d.d...@gmail.com> > Hi John, > > 2.0.0-beta3 predates the changes which fix this issue. The message is > benign > and can safely be ignored. You could merge the changes for revision > 923929<http://svn.apache.org/viewcvs?view=rev&rev=923929> back > to your copy of the source if you want - that should fix the problem. > > Regards, > -mike > > On Mon, May 17, 2010 at 9:54 AM, Web developer <webautomat...@gmail.com > >wrote: > > > My version is 2.0.0. Extracted from > apache-openjpa-2.0.0-beta3-binary.zip. > > Thanks! John > > > > 2010/5/17 Michael Dick <michael.d.d...@gmail.com> > > > > > Hi > > > > > > Which version of OpenJPA are you building? Last month (IIRC) we removed > > the > > > openjpa.loglevel property from the builds (1.2.x - trunk). If you have > an > > > older version of one of the pom.xml files it might still show up > though. > > > > > > FWIW the changes were done under > > > OPENJPA-1557<https://issues.apache.org/jira/browse/OPENJPA-1557> > > > . > > > > > > -mike > > > > > > On Mon, May 17, 2010 at 5:54 AM, Web developer < > webautomat...@gmail.com > > > >wrote: > > > > > > > Got the following notice when trying to run tests: > > > > > > > > enhance.all.entities: > > > > [echo] running enhancer > > > > 160 WARN [main] openjpa.Runtime - The configuration property named > > > > "openjpa.loglevel" was not recognized and will be ignored, although > the > > > > name > > > > closely matches a valid property called "openjpa.Log". > > > > > > > > Logging not configured properly? John > > > > > > > > > >
