I'm sorry, William. I just realized that in both examples you were
talking about not calling ejbStore. On first reading, I thought you
were referring to the ejbLoad behavior in the "read-only cache"
example. My bad!
You are correct; this is a violation of the specification.
-Dan
>
>
> On 10 Apr 00, at 8:40, Louth, William (Exchange) wrote:
>
> >
> > read-only cache strategy
> >
> > The read-only cache strategy can be used for entity EJBs that are never
> > modified by an EJB client, but may be updated periodically by an external
> > source. For example, a read-only entity EJB may be used to represent a stock
> > quote for a particular company, which is updated externally to the WebLogic
> > Server system.
> >
> > WebLogic Server never calls ejbStore() for a read-only entity EJB. ejbLoad()
> > is called initially when the EJB is created; afterwards, WebLogic Server
> > calls ejbLoad() only at intervals defined by the read-timeout-seconds
> > deployment parameter.
> >
> The read-only cache strategy does not violate the specification.
> Section 9.1.1.0 specifically allows this behavior as commit option
> "A":
>
> "The Container caches a ready instance between transactions. The
> Container ensures that the instance has exclusive access to the
> state of the object in the persistent storage. Therefore, the
> Container does not have to synchronize the instance�s state from
> the persistent storage at the beginning of the next transaction."
>
> The timeout-interval is clearly allowed because the server is
> allowed to call ejbLoad at any "arbitrary" time, according to the
> specification.
>
> -Dan
>
>
===========================================================================
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".
