"Willecke, Dirk" wrote: > >> > >> But coincidentally the container could have passivated the bean. > > > >An entity bean involved in a running transaction cannot be passivated. > > I think you're wrong. The specification says: > > "The container can choose to passivate an entity bean instance within a > transaction. To passivate an instance, the container first invokes the > ejbStore method to allow the instance to synchronize the database state > with the instance's state, and then the ejbPassivate method to return > the instance to the pooled state." (Chapter 9, Entity Bean Component > Contract) > My bad. I was thinking of stateful session beans.
begin:vcard n:Wilson;Chip tel;fax:(214) 358-0353 tel;work:(214) 642-4559 x-mozilla-html:TRUE url:http://www.axyssolutions.com/ org:Axys Solutions adr:;;;Dallas;TX;; version:2.1 email;internet:[EMAIL PROTECTED] title:Application Architect note:Sun Certified Java Architect x-mozilla-cpt:;-25088 fn:Chip Wilson end:vcard
