If your entity bean consists of a mixture of NULLable and NON NULL fields, how
will you handle? Will you declare NON NULL fields as basic data types and
NULLable fields as wrapper classes (Float, Integer etc). Or will you uniformly
declare all fields using wrapper classes only.
--
shiv
[EMAIL PROTECTED]
Avi Kivity wrote:
> > I have an entity bean with two container managed int fields,
> > both nullable. If I
> > declare both of them as 'int' data types, there is no way I
> > can find if they are
> > null or not. I was wondering how others handle this
> > situation. Declaring both
> > the container managed fields as java.lang.Integer seems to be the most
> > straightforward solution. Pl let me know if there is any
> > other way to handle
> > this.
> >
> java.lang.Integer is what I use.
>
__________________________________________________
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".
