Will Dazey

These appear to all be negative tests; expecting failures that didn't occur. These tests appear to expect to be run in a specific order and have skated by in the...

@rfelcman @lukasj I dug in much deeper and I am starting to wonder if these tests are just obsolete. We seem have to have good coverage of `EntityManager.getReference()` in `eclipselink.jpa.test`...

Seems like the same issue I am attempting to look into for SQLServer: https://bugs.eclipse.org/bugs/show_bug.cgi?id=579409

@katzyn That's probably the correct strategy, but EclipseLink is rather committed to the 2 query process. It'll take a rewrite to add that functionality.

@lukasj Unfortunately, the process to obtain the sequence number is decoupled from the process that handles the INSERT. EclipseLink first performs the INSERT, then once that is complete, the process...

It appears that `org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializer.getJavaSECMPInitializer` also has this issue on 2.6_WAS: https://github.com/eclipse-ee4j/eclipselink/blob/2.6_WAS/jpa/org.eclipse.persistence.jpa/src/org/eclipse/persistence/internal/jpa/deployment/JavaSECMPInitializer.java#L61 For 2.7+, it looks like @lukasj fixed the issue in this commit: https://github.com/eclipse-ee4j/eclipselink/commit/05ffcf76bab398c5360f2789203a34b70eb46791

@lukasj Is there a reason for dropping support for Oracle 9 and older? Is it getting in the way of something? Also, it looks like you are removing Oracle10 too.

@jgrassel Can you include the DDL for the table generation?

@FabriSr Hello! Thank you for bringing this issue to our attention! Have you noticed this issue recently in a previously functioning application (regression) or are you investigating a new application...

@FabriSr > EclipseLink is failing to track changes when an entity has an embedded collection property mapped using Set's: > whenever an entity instance is read from the entity manager...