Ok. but fyi if the plan is soon to release 2.2.1 then perhaps someone needs to look into it because 2.2.0 didn't have this problem
-- View this message in context: http://openjpa.208410.n2.nabble.com/JDK-1-7-seems-to-be-causing-an-issue-with-latest-snapshot-tp7581417p7581426.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
