I use hibernate 3.5.4-Final as my JPA 2.0 persistence implementation and everything works just fine until I try to send lazily initialized objects over the RemoteInitialContextFactory as explained here: http://openejb.979440.n4.nabble.com/Error-reading-response-from-server-OEJP-3-1-with-3-2-SNAPSHOT-td2323297.html#a2323297.
I know there is the https://jira.jboss.org/jira/browse/EJBTHREE-440 issue caused by the bug in the JVM, but since it was solved in the 3.0-final version I guess the problem _probably_ comes from somewhere else now. Is it possible that the reason is that openejb doesn't know how to handle third parties providers' proxies on the client side, since it has always used OpenJPA as the default provider before the latest 3.2-SNAPSHOT (with JPA2 support)? -- View this message in context: http://openejb.979440.n4.nabble.com/OpenEJB-client-jar-with-non-OpenJPA-persistence-providers-tp2335151p2335151.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
