It's not for the specification to say whether or not ordering takes place at
the resource or in the EJB container. That's up to the vendor.
The point is: The ORDER BY clause is needed so that the bean developer and
clearly communicate the ordering requirements to the EJB container's deployment
tools.
I think that most EJB vendors will push ordering down to the resource, but
whether they do that or not isn't important to the specification. What's
important is that EJB QL provide an ORDER BY clause, because ordering is
fundamental to the query paradigm, and because developers will need it.
--
Richard Monson-Haefel
Author of Enterprise JavaBeans, 2nd Edition (O'Reilly 2000)
Co-Author of Java Message Service (O'Reilly 2000)
http://www.jMiddleware.com
===========================================================================
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".
