Thanks, Romain.

Now see, that's really weird. I had fully expected the pages I create to fail. But instead, they actually load data! That's the part where I'm lost as to why. I have not added the Derby Client jar to the project, you see. And I know, with MySQL for example, I always have to do that or put it in the lib folder of TomEE. Yeah, that's why I'm shaking my head.

Here's the server log (I'm running this in an isolated VM): http://pastebin.com/njYwB3zP

Find the line that reads:
PersistenceUnit(name=TestAppPU, provider=org.apache.openjpa.persistence.PersistenceProviderImpl)
Is that supposed to be the JDBC provider?

I'd be happy if someone could clarify this for me.

Kay


On 07/15/2014 10:34 AM, Romain Manni-Bucau wrote:
Hi

Not it is not but ensure (through JMX for instance) the datasource is
not using hsqldb (our default which is in tomee out of the box).

You also get the information in the logs 'adjusting ...' during startup


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-07-15 17:22 GMT+02:00 Kay Wrobel <[email protected]>:
I am testing TomEE and NetBeans right now, and am a little perplexed as to
why my application works. When I use MySQL, I normally have to include the
mysql driver jar in my project OR copy the jar to the TomEE lib directory or
else the application won't be able to connect. Naturally, I thought the same
for the JavaDB drivers. But it seems that I don't have the Derby Client
library added to my project and in fact it is not in my project's lib
folder, nor is it in the TomEE lib folder.

So I guess my question to either of the two groups is: does OpenJPA / TomEE
ship with its own Derby client library?

Thanks.

Kay

Reply via email to