Hi Jim,
I finally got to the bottom of the issue. There definitely was a bug,
but it was in OpenEJB 3.0. We must have inadvertently fixed it when
we did the stateful container rework between 3.0 and 3.1.
It took me a while to notice this because of all the parent/child
names in the samp
Hi Jim,
Wanted to give you an update. I've been looking into this one and so
far haven't been able to find the source of the issue. In addition to
your sample I've been adding more tests in this area -- the java ee
tck has plenty but it's nice to have some of our own.
Seems the basic fu
On Nov 21, 2008, at 3:04 PM, JimOR wrote:
David,
Looks like OpenEJB3.1 is the culprit. EJB3.0 with JPA 1.0.1, 1.1,
1.2 and
1.3-SNAPSHOT work as expected, but 3.1 with any of the JPA jars fails.
This sample http://www.nabble.com/file/p20631026/sample.zip
sample.zip
should give you a hea
hould be good to go.
The sample/test folder contains the junit xml results of the test case under
the various classpaths.
Thanks for your help,
Jim
--
View this message in context:
http://www.nabble.com/EntityManager-Propagation-Problem-under-3.1-tp20571571p20631026.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
On Nov 18, 2008, at 4:29 PM, JimOR wrote:
Apologies in advance for cross-posting, but my post to OpenJPA (
http://n2.nabble.com/EntityManager-Propagation-with-Extended-PersistenceContext-td1495977.html
http://n2.nabble.com/EntityManager-Propagation-with-Extended-PersistenceContext-td1495977.ht
ntity.Parent-6264
Please help
Thanks,
Jim
--
View this message in context:
http://www.nabble.com/EntityManager-Propagation-Problem-under-3.1-tp20571571p20571571.html
Sent from the OpenEJB User mailing list archive at Nabble.com.
