I'm using Glassfish v3 as app server, Java EE 6 Web, JSF and EclipseLink (JPA 2.0). My project was working just fine, redeploying was no problem, even if I deleted a table from my database EclipseLink would regenerate it without any hassle. But now when I drop a table from my database it will give me the following error:
I deleted and remade my persistance units, which didn't seem to affect. I had an unused realm defined on the server, I deleted that. It's back to normal now... I had that realm defined since a while but looks like it messed with my Glassfish-v3 at some point.
I still couldn't figure out what exactly coused it.
I have a persistance unit that has table generation strategy as "Create" and a version of it with the "Drop and Create". Now most tables have the Create one and then another one has got
So I cannot use them together?
I think this problem started after I tried to have a third persistence unit that used a different JNDI and Connection pool (which was for another schema). I was trying to have my application persist from 2 different schemas (from same MySQL server though).
Joined: Oct 01, 2007
If they have different schema/tables it is fine. But if they share the same tables, then one will be dropping the others tables.