I realise that the original reasoning for this was security
This and also a general desire to encapsulate as many server details
as possible.
this presents a challenge for utilising EJBQ
EJBQL should work without knowledge of DbEntity. What errors are you
getting? We may be able to fix by fixing processing pipeline.
Andrus
On Jan 25, 2010, at 12:51 AM, Lachlan Deck wrote:
Hi there,
ObjEntity.getDbEntityName() in ROP returns null as does DbEntity. I
realise that the original reasoning for this was security but this
presents a challenge for utilising EJBQL (or SQLTemplate for that
matter) to some extent from ROP.
Two immediate problems:
- if the ROP code only knows the name of the ObjEntity this won't
necessarily map to the same name in the DbEntity/ or table/view.
- same again goes for attribute names.
etc
Is it worth rethinking this for 3.1?
with regards,
--
Lachlan Deck
