>
1. Byte-code weaving of the domain classes. In the standard class-loader configuration the domain classes will be woven once and only once. If this weaving is consistent across all persistence units and test that might share the domain class then you are fine but if the same class is used differently in different PUs then you will be challenged to have separate woven instances of the class isolated by the PU/test-case.
I figured this would be the case. I'm looking more at the middle of the road case. I assume a huge majority of cases can be covered with a default weaving configuration? That being said, I'm not very familiar with the EclipseLink weaving options to know how many different switches there are and how many of them are used in the wild.
> there is also the fundamental case that you are now testing a configuration that is separate from the JPA specified one.
True. Testing in this manner would exclude handling / parsing of p.xml files etc, but it would make adding tests for the rest of the runtime much simpler.
> I do have a number of dynamic PU examples I had built locally that I will review and see how best to share.
I'd appreciate you sharing those. I assume these examples use features that are already a part of EclipseLink?