>
> 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.
>
I declare nullable fields as object types and non-nullable fields as
primitive types, both to help me remember when I need to check for null, and
because I really hate the primitive wrapper classes.
- Avi
--
s/\be(\w+)/e-\1/g;
===========================================================================
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".
