On Tue, 2002-10-29 at 17:28, Bill Burke wrote:
> JBoss is being used in production everywhere.  I've been at 6 sites myself
> over the past year.  IMHO and experience, entity beans are not the right
> choice if you're doing complex reporting.  A handmade query cache with
> direct JDBC will always be faster.  Besides, EJB QL doesn't have Group By.

Regarding Bill's comment about reporting; this is *so* true.  IMHO this
is one of the biggest problems that needs to be addressed in the EJB
spec.

However dropping to JDBC is not the answer either.  Unfortunately, there
is currently little choice.

What is needed is the ability to run queries directly in EJB-QL.  Having
to use JDBC means your application is dependent on the database domain.
In other words, the application designer has to know about the
implementation specifics of the persistence layer (database). 

Being able to execute queries in EJB-QL would allow us to use bean names
and property names. 

-- 
Peter Beck BEng (hons)  - Managing Director, Electrostrata Ltd.
http://www.electrostrata.com  --+-+--  Experts in e-business and
e-commerce



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to