On Mon, 19 Feb 2001, you wrote:
> Well, I have tried out the same program with Weblogic, which generates a
> FinderException. That's why I thought Jboss too ought to generate the same.
> I didn't know that the documented behaviour isn't so. Sorry, and thanx.
> -Prince
Hmm, if that's what weblogic does, then weblogic is wrong. Section 9.1.9.3 of
the spec says:
> From the client's perspective, a FinderException (or a subclass of
> FinderException) indi- cates that an application level error occurred during
> the find(...) operation. Typically, the client's transaction has not been
> marked for rollback because of the FinderException.
Not finding any instances is not really an application exception, and so a
plain FinderException is not the answer. Section 9.19.4 is stronger:
> Only single-object finders (see Subsection 9.1.8) should throw this exception
> [ObjectNotFoundException]. Multi-object finders must not throw this exception.
> Multi-object finders should return an empty collection as an indication that
> no matching objects were found.
So that'd be why JBoss behaves like it does.
Cheers
Tom
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
