As Jay mention, for EJB 2.0 we have (page 130)
Once the primary key for an entity bean has been set, the Bean Provider must
not attempt to
change it by use of set accessor methods on the primary key cmp-fields. The
Bean Provider
should therefore not expose the set accessor methods for the primary key
cmp-fields in the
component interface of the entity bean.
Maybe do we need a Verifier task to check that and warn the user. Just to
be sure . . .
Vincent.
ps:i can help on jaws, my 10 fingers are yours
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de
> danch
> Envoye : lundi 7 mai 2001 23:46
> A : [EMAIL PROTECTED]
> Objet : Re: [JBoss-dev] TODO: JBossCMP 1.1 FAST!
>
>
> Bill Burke wrote:
>
> > BTW, running with tuned updates off is really, really, bad. With tuned
> > updates off, CMP will update your primary keys as well.
> Updating primary
> > keys is a crazy thing to do because the database needs to
> obtain write-locks
> > on any indexes/constraints attached to that row/table. This can
> cause major
> > deadlock problems fairly easily with multiple concurrent users. Has the
> > update of primary keys in CMP been removed? I know there was some talk
> > about it.
> >
>
> If I hear no objections, I'll get rid of the code attempting to update
> the primary key columns.
>
> -danch
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
