I was wondering about this as well. Also, does binding a single jdo to the jndi pretty much eliminate the benefits of having a connection pool.
"Mutchler, Scott"
<Scott.Mutchler@Bell To: [EMAIL PROTECTED]
South.com> cc:
Subject: [castor-dev] JDO: Object
Cache and JNDI...
12/04/2001 12:21 PM
Please respond to
castor-dev
I have some stateless Session Beans that use JDO. I want to bind (and
rebind) the JDO object to JNDI. However, it appears that as soon as I do
that... long transactions stop working. Is it possible that when I bind
the JDO object the object cache is wiped out (I am using WebLogic 5.1)?
Perhaps the JDO object is serialized?
The code works fine if I don't bind the object to JNDI but then the
Session Bean cannot be stateless. In short, I need a way to use JDO
in a stateless object [EJB] but be able to preserve the object cache
so that I can use long transactions. Please don't point me to the
online documentation, as I have read it already. Thanks.
Scott(See attached file: Glacier Bkgrd.jpg)
<<attachment: Glacier Bkgrd.jpg>>
