Excellent question!!! Enterprise Java Beans (OReilly) suggests creating
a validation Object. He uses a zip code object as an example.
public class ZipCode implements Serializable throws ValidationException{
public ZipCode() {throw new ValidationException("Zip Code cannot be
null");}
public ZipCode (...)
public ZipCode (...)
}
You can then use this object to pass around, you can also change the
validation without changing the Entity. Even though it didn't have much
more information, it seems that you can dissect the class in a session
bean before placing it in an entity with primitives.
: )
--
Dan Hinojosa
Java & Lotus Notes Consultant
Java Certified Programmer
P.O. Box 4675
Albuquerque, NM 87196-4675
Telephone: (505) 262-0911
Email: [EMAIL PROTECTED]
WWW: http://www.digitalpriest.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".
