Hi, I would like to know how people handle SQL unique constraints in EJB. Let's say I am creating a User Entity Bean. In the table, the username must be unique. Now, when I try to create a User Entity Bean with a non-unique username, I got an SQL exception. Unfortunately, this exception is wrapped in some RuntimeException and there's no way to catch it. Does that mean I have to implement the logic of all of my SQL constraints in my session bean facade? Or is there a better way to do it? Thanks Charles __________________________________________________ Do You Yahoo!? Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.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".
