u can do either only advantage of the pk class will come when it is not
one of those primitive types and also when it is composite key
dipin
On Tue, 1 Aug 2000, vihs wrote:
> 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".
