Hello Klaus,
Maybe you have exclusive-write-access="true" in <entity-deployment> in
orion-ejb-jar.xml? This is the default and allows for optimizations like
the one you see, but is based on the fact that there's only one party
writing to the DB. Try setting exclusive-write-access="false" and see if
that helps. Otherwise, contact bugs@ again.
Regards,
Karl Avedal
Klaus Thiele wrote:
> Hello,
>
> i just discovered, that the ejbLoad() method was
> NOT called at the second (and subsequent) calls to the
> remote methods (BMP).
> (until an passivation or ejbStore is done).
>
> yes, i checked the ejb-jar.xml for correct container-transaction's.
> with the j2sdkee it works correct!
>
> first call:
> == pgrdatEJB: setEntityContext()
> == pgrdatEJB: ejbFindByPrimaryKey(002|006|3330|1999-01-01)
> == pgrdatEJB: ejbActivate(2063956369, PK = 002|006|3330|1999-01-01)
> == pgrdatEJB: ejbLoad(2063956369, PK = 002|006|3330|1999-01-01)
>
> ... changing the row from outside ...
>
> next call(s):
> == pgrdatEJB: setEntityContext()
> == pgrdatEJB: ejbFindByPrimaryKey(002|006|3330|1999-01-01)
> thats it!!! - the client got the old data!!!
>
> any hints?
>
> thanks a lot
> klaus
>
> ps: tested with 1.0.3b and 1.2.0
>
> --
> Klaus Thiele - Personal & Informatik AG
> mailto:[EMAIL PROTECTED]
>
> "There's got to be more to life than compile-and-go."
