this seems to be an error in the API docs (guess someone forgot to clean
up). The finder should return an empty collection (meaning a non-null
Collection reference with size() == 0). If I remember correctly that
ambiguity in ejb 1.0 was criticised and therefor clarified as most people
consider the empty collection approach the cleaner one. All ejb servers I
have worked with implement it that way when using CMP.
regards,
robert
At 22:10 16.02.2001 , Wong Kok Wai wrote:
>I'm a bit confused what should be returned by finders that return
>multiple objects. In the EJB 1.1 specs, it is stated an empty collection
>should be returned. However, in the JavaDocs for
>ObjectNotFoundException, it is stated a null collection should be
>returned. My understanding is null collection is null, and an empty
>collection is a collection with zero elements. So which should I return
>(I prefer the empty collection approach, as it simplifies both the bean
>and client implementations)?
>
>===========================================================================
>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".
(-) Robert Krüger
(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
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".
