What is the reason to not allow java.util.List as a valid return type for
finders? This forces us to frequently write semantically incorrect programs
as we rely on the order of items in the collection (because any O/R layer I
know allows to specify the order for CMP finders). Why not allow List as a
return type to get rid of this IMHO unnecessary incorrectness? Same holds
for collection valued CMR fields. I disagree with the assessment that
relying on the order of things is bad practice and agree with people
arguing for an ORDER BY clause in EJB-QL in the thread started by RMH. I
just don't see why? Looking at all EJB applications I've worked with for
the past 2 years, I think this is completely against common practice and I
don't even see a semantical problem with using ordered collections for
finder results (and CMR fields btw). How many persistent stores that CMP
engines are build on top of don't support ordering of query results? What
this will lead to is that container providers will probably provide
additional means to specify an order for finders because people need it,
which again will lead to non-portable apps.
Regards,
Robert
(-) 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".
