-
1. Re: Move *HibernateSession to a Proxy implementation
bill.burke Mar 22, 2007 2:52 PM (in response to epbernard)Lol, yeah, you're right....Not sure why I did it that way to begin with. Either I was just being stupid, or at one time I had to intercept specific methods.
-
2. Re: Move *HibernateSession to a Proxy implementation
brian.stansberry Mar 22, 2007 5:33 PM (in response to epbernard)For fine-grained replication of SFSBs that have an XPC, we'd talked about fine-grained replication of the EM. Will this make that impossible?
-
3. Re: Move *HibernateSession to a Proxy implementation
epbernard Mar 22, 2007 5:38 PM (in response to epbernard)No it should not have any impact. The proxy can be ignored by the "serialization", you want to replicate the underlying EM
-
4. Re: Move *HibernateSession to a Proxy implementation
epbernard Mar 22, 2007 6:06 PM (in response to epbernard)Where is ExtendedPersistenceContext.getFactory() (return an ManagedEntityManagerFactory) used?
EJB 3.0 does not seem to use it and it conflicts with o.h.e.SessionImplementor.getFactory() (returns a SessionFactoryImplementor)
Can I get rid of it? -
5. Re: Move *HibernateSession to a Proxy implementation
bill.burke Mar 22, 2007 8:12 PM (in response to epbernard)looks like an artifact. I'll remove it and put in the proxy implementation too. Just let me get a clean checkout. My wc is really old.
-
6. Re: Move *HibernateSession to a Proxy implementation
epbernard Mar 22, 2007 8:24 PM (in response to epbernard)I am almost done actually already
I am passing the tests
stateful is having issues, I need to investigate -
7. Re: Move *HibernateSession to a Proxy implementation
epbernard Mar 22, 2007 9:48 PM (in response to epbernard)Done in both head and 4.2
I also removed
ExtendedPersistenceContext.getFactory()
I used a JDK Proxy generation approach if someone want to use Javassist, feel free.