Yes, you can add your own dirty-checking by adding a:
public boolean isModified() { ... }
method to your bean, sorry for this being poorly documented.
However Orion should *not* call ejbStore() after each call
under normal conditions - it has a built-in mechanism to try
and decide if the bean data has been updated. Which version
of Orion are you running and what type of member fields does
your bean contain?
/Magnus Stenman, the Orion team
----- Original Message -----
From: "Elliot, David (NOW)" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Saturday, February 12, 2000 8:34 PM
Subject: Suppressing container calls to EJBStore() ??
> Hi all,
>
> Is it possible to control which method calls to an entity bean (BMP)
> trigger the container to call the bean's EJBStore() method?
>
> Currently Orion appears to be synchronizing my entity beans (calls
> EJBStore() )
> after each and every method call...
>
> I'd like to avoid having EJBStore() called after "read-only" method
> calls to a bean that are guaranteed not to have modified that bean's
> state (therefor a database write transaction is not required...).
>
> Thoughts ??
>
> Dave Elliot
> Web Developer
> [EMAIL PROTECTED]
>
>
>
>
