Well, you didn't mention that you had a test case that proved otherwise... :-) I thought you were just asking about the documentation.
If your assessment is accurate, then this sounds like a spec compliance issue -- which I am surprised hasn't been discovered until now. If you could package together a simple junit testcase that demonstrates this scenario, then we should take a closer look. A JIRA [1] would also be good, if you access to that. Thanks, Kevin [1] http://issues.apache.org/jira/browse/OPENJPA On Mon, Nov 7, 2011 at 5:59 PM, areider <open...@reider.net> wrote: > Kevin, > > I can see that interpretation, but I'm not only going by the doc, it > actually seems to be doing that validation at persist() time and throwing > the TransactionRequiredException, even though the em is marked as > persistenceContextType.EXTENDED... so unless i'm missing something, it > seems > as if it is doing the transaction-required check when it shouldn't be ... > > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/TransactionRequiredException-on-persist-on-extended-EM-tp6972526p6972602.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
