Hmmm, AFAIK, EJB3 PR allows List as return type as long as @OrderBy is specified?
Can anybody say, whether this (at least wrt. to jboss/hibernate) requires more resources, results in a worse performance than with a simple Collection ?
In my simple world ;-), I would assume, that hibernate just uses the given return type and just calls *.add("ResultSet") and so there would be no overhead (neglecting the overhead of the initial DB order fragment) ... If this is the case, one could even use more specific return types like ArrayList, PriorityQueue, etc. , right ?
