Jay,
Correct me if I'm wrong, but I think you are supposing you have some
fields in your entity bean that act as primary key, is this right?
regards
Jose
Jay Walters wrote:
> To keep ejb-interest from becoming a ghost town I'll ask a question with I
> am hoping an obvious answer.
>
> In looking at the EJB 1.1 spec I don't see anything that keeps me, a bean
> writer from changing the primary key fields within my entity bean (BMP or
> CMP); there is at least one container that would propagate these changes to
> a CMP entity bean into the database.
>
> My question is, since the primary key associated with the bean doesn't
> change; and in general we shouldn't be changing the identity of a bean in
> midstream, shouldn't the container or the CMP persistence manager complain
> about this? Or at the least shouldn't there be something in the spec about
> not doing this when writing an entity bean? Otherwise locating the bean by
> primary key will be sort of a hit or miss thing depending on whether it's
> been re-loaded since the primary key in the bean is updated.
>
> Cheers
> Jay Walters
>
> ===========================================================================
> 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".
