Luke,
search the previous posts for the following topic "HOW TO DISABLE
ENTITY-BEAN CACHING". You can read about the steps I had to take in order
to eliminate caching with option-C. I still think setting the container to
"option-C" alone should have disabled caching...does anyone know if there is
a bug with the LRUCachingPolicy?
Frank T. Villarreal, Jr.
Email [EMAIL PROTECTED]
> -----Original Message-----
> From: Luke Studley [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, July 19, 2001 7:35 AM
> To: '[EMAIL PROTECTED]'
> Subject: Re: [JBoss-user] ejbLoad not called even when
> commit-option is
> C
>
>
> Hello
>
> I think this relates exactly to the same problem I am having,
> see my post
> from about 18 hours ago below. When I went back to read the
> ejb1.1. spec it
> seems to suggest that there are 3 different ways a container
> may behave
> between transactional calls on a bean (see mail below), it
> appears to me
> that JBoss is taking option A, which is allowable, but not
> very useful for
> what I want to achieve (i.e. dB access from without the bean).
>
> I am hoping that somebody will rubbish my conclusions and
> tell me how we can
> make JBoss call ejbLoad at the beginning of each
> transactional set of calls.
>
> If you find any solution to this please do post it.
>
> Best of luck
>
> Luke
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
