Cedric,
There is nothing stopping you from putting the queries in a stateless
session bean at present but it means that you would have to craft your
own SQL or use a third party product to do it for you. The advantage of
using the method I have set out is that it would all be container
managed, making use of all the existing semantics and compilation checks
that are part of the specification today.
I like your idea of making the view objects able to access more than one
entity bean.
You could make the view objects returned updateable but this would start
making the technique quite heavyweight in nature (perhaps as you say -
it could be optional). The value I see in view objects would be for
gathering subsets of data to pass on up to the viewing tier - without
having to get involved with low-level SQL and JDBC.
Myles
===========================================================================
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".
