Well I don't necessarily feel I can handle it, :-), since your message has
me thinking that I'm missing something. Are you saying there are places
other than ejbLoad() where you have to use contect.getPrimaryKey() or risk
being out of sync?
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Rickard �berg
> Sent: Friday, January 21, 2000 7:15 AM
> To: [EMAIL PROTECTED]
> Subject: Re: petstore: storing the userId
>
>
> Hi!
>
> Colin Sampaleanu wrote:
> > Sorry if I am being dense, but what is the problem as long as
> in ejbLoad()
> > it uses context.getPrimaryKey() (which it does)? How can it get
> out of sync
> > with the real key, or rather, how can this make it possible to shoot
> > yourself in the foot?
>
> The problem is if you forget that you're a BMP bean and don't use
> getPrimaryKey, but the attribute in the bean. Then you're gonna get
> weeeird behaviour. At least when EJB was new I saw lots of people having
> trouble with this (they didn't understand the instance reuse scheme).
>
> If you feel you can handle it, then by all means, go ahead :-) I just
> don't trust myself enough to do that :-)
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.dreambean.com
> Question reality
>
> ==================================================================
> =========
> 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".
