Will need to investigate that. Could be a bug. IIRC we officially
supported EJBQL on the client.
Andrus
On Jan 26, 2010, at 2:10 AM, Lachlan Deck wrote:
On 25/01/2010, at 6:19 PM, Andrus Adamchik wrote:
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.
If you use a simple query such as 'SELECT COUNT(a) FROM
SomeEntityName....' the error returned is that no such Table/View
exists.
with regards,
--
Lachlan Deck
