Which means you would be even MORE chatty then a normal EntityBean.
Normally ejbStore() would only be called on a tx boundry. If you do this,
you will call ejbStore() for every changed property. ALOT more chatty then
a normal EntityBean.
Dave Wolf
Internet Applications Division
Sybase
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Cedric Beust
> Sent: Wednesday, September 13, 2000 4:08 AM
> To: [EMAIL PROTECTED]
> Subject: Re: How to update a BMP?
>
>
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Kjetil Helgaker Paulsen
>
> > And how do you detect when a update is needed?
>
> Keep track of what fields have been modified, e.g. with a bitmask.
>
> --
> Cedric
>
> ==================================================================
> =========
> 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".
>
>
===========================================================================
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".
