> From: Jonathan Weedon [mailto:[EMAIL PROTECTED]]
> That's broken. I can't show you how it violates the EJB spec
... which should be an indication that it doesn't :-)
Your business method will execute fine, it will return a key that might not
exist at this point in time in the database, but it would violate the
specification to throw NoSuchObjectException at this moment.
Therefore, we don't.
A typical example where such behavior is desirable is this: the process
that deleted the row in the database intends to replace it with another one
with a similar key. You don't want your client to fail at this point
because even though the object fugitively disappears from the database, your
application is still operational.
--
Cedric
===========================================================================
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".
