it appears that session.load throws a HibernateException if an object
with the supplied id doesn't exist.  would it be better for hibernate to
throw a different exception in this case (say an ObjectNotFoundException
that extends HibernateException), to differentiate between the object
not existing and some other error?  or is the expectation simply that a
find query is to be used if u r not sure if a particular persisted
object exists?

thanx

brad

> _______________________________
> brad clow
> chief technical officer
> workingmouse
> 
> email: [EMAIL PROTECTED]
> web:   http://www.workingmouse.com
> 

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to