Its my understanding that a single field primary key can be a String or
primitive wrapper or any Java RMI-IIOP compliant class that can be
mapped to a corresponding field in the bean class. This means, for
example, that an Integer class could be a primary key, but so could
java.math.BigInteger or a java.security.Principal serializable
implementation (purely illustrative example). In sort any class that is
serializable, compliant to Java RMI-IIOP value types, and implements
hashCode and equals appropriately can be a single field primary key.
While a primitive wrapper can be single field primary key, a primitive
type (int, long, double, etc.) can not. This seems to be true because
of the semantics of the ejbCreate( ) and EJBObject.getPrimaryKey( )
which require that a object type be returned. (CMP bean must return null
from ejbCreate( ), which won't work if the key is a primitive.)
I'm looking for a confirmation of these assumptions from a Sun EJB
authority, but I have posted this to the EJB-INTEREST because I believe
this information will benefit the enter community.
--
Richard Monson-Haefel
EJB Expert for jGuru.com
( http://www.jguru.com )
Author of Enterprise JavaBeans
Published by O'Reilly & Associates
( http://www.ejbnow.com )
===========================================================================
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".
