Description Sabine Heider 2009-11-23 05:37:40 EST

Created attachment 152834 [details]
Patch containing explicit settings for eclipselink.target-database and eclipselink.weaving

Currently, the JPA tests pass the database platform and weaving related
settings as VM parameters to the test environment. While this works for
stand-alone tests, I have experienced problems in the application server case
where the tests are executed in the server's VM and therefore default values
for the database platform and weaving apply. 
For the database platform, this lead to failing tests due to incorrectly
generated SQL when running against a MySQL database. 
For weaving, a lot of tests failed on the NetWeaver application server because
it does not support dynamic weaving.

My suggestion would be to make both the database platform and the weaving
explicit in the persistence.xml file of the deployed test application. I have
attached a patch with the proposed change. 

Naturally, I don't have all the supported application servers at hand, so I
couldn't test the change there but tested it on NetWeaver only. I will install
a glassfish to cover a second platform and update this ticket (if no one else
confirms the patch until then).