Aaron Mulder wrote:
> I've got a session bean that changes an entity bean. The session
> bean has no data sources defined, though the entity does. When my call to
> the session finishes, the TxCapsule calls the
> EntitySynchronizationInterceptor which calls the BMPPersistenceManager
> which calls store on the entity. When the entity tries to look up its DB
> pool to get a connection, it fails. However, if I add a resource
> reference to the session bean, then the entity succeeds. So it looks like
> the java:comp/env environment is not being reset to that of the entity
> when the entity is stored - it stays set to the session bean's
> environment. Any thoughts?
I think I figured it out. During the commit phase the persistence
manager must set the right context classloader prior to calling
ejbStore, or else you will get the above problem.
Either I will fix this on Monday (going away over the weekend), or
someone else can take it. Should be pretty trivial to fix.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
