Hi Tyler, sorry to bother you, but can you tell me from where it is originated, or for which version of weblogic is it true? We are using weblogic 5.1 and following text is written in dtd: (http://www.bea.com/servers/wls510/dtd/weblogic-ejb-jar.dtd)
<!-- Applicable to entity beans only (both container- and bean-managed). This optional optimization affects whether the bean is loaded immediately into the cache (followed by invoke of ejbLoad) after a call to a finder returns a reference to a bean. If this is set to "True", the bean will immediately be loaded into the cache if a reference to a bean is returned by the finder. If this is set to "False", the bean will not be loaded into the cache until the first invoke of the bean. The default value is "False", which supports the behavior indicated by the EJB 1.1 specification. Used in: persistence-descriptor --> <!ELEMENT finders-call-ejbload (#PCDATA)> So, it is in opposite to the statement you sent. What is really true? Thanks Rah > -----Original Message----- > From: Tyler Jewell [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 19, 2001 8:55 PM > To: [EMAIL PROTECTED] > Subject: Re: Removing a CMP Entity Bean from Memory > > > This isn't quite accurate either, but definitely along the right idea: > > <vendor> > > WebLogic does aggressive loading of fields by default since > <finders-load-bean> is defaulted to true. This means that a > finder query > will be expanded to load all of the matching fields and PKs > in one trip to > the DB. If the finder returns a query that is larger than > the cache limit, > the cache will be filled with as many as possible. If > <finders-load-bean> > is set to false, a finder method will return a Collection > with PKs, but > ejbLoad() will not be called until a getXXX() method is > specifically called. > This situation is ideal when you only want to do updates and > reading the > data is not necessary. > > WebLogic leaves instances in cache and it's in the server's > best interest to > keep cache filled. When you do a findByPrimaryKey(PK), > WebLogic checks to > see if the PK is already in cache and not in a TX. If it > isn't, the DB hit > isn't done, the cache object is returned to the client. When > the client > accesses one of the fields, an ejbLoad() will be done if necessary. > > </vendor> > ==========================================================================To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
