Hi,
Having generic wrapper classes as PKs are great, however they are not
typesafe. Once your application has tens or hundres of bean classes, and
your session beans use them via PKs, you will see what I mean!
Gene
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of vihs
Sent: Tuesday, August 01, 2000 12:54 AM
To: [EMAIL PROTECTED]
Subject: int as Primary Key
Hi all
I have only one column of datatype 'int' as the primary key for my entity
bean.
I have two options now :
* Define a new class called BeanPK and specify the class name in
<prim-key-class> element in ejb-jar.xml
* Define a container managed field of type java.lang.Integer in the bean
class. In ejb-jar.xml specify the following
<prim-key-class>java.lang.Integer</prim-key-class>
..
<primkey-field>containerManagedFieldName</primkey-field>
This way I can save writing a new PK class.
Any advantages/disadvantages following either type?
TIA.
--
shiv
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.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".
===========================================================================
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".
