From: Michael Bouschen <Michael.Bouschen_at_Sun.COM>
Date: Fri, 13 Jan 2006 15:26:15 +0100

Hi Tom,

I think I have a fix for the EJBQL problem with an IN-expression
including an input parameter:
   SELECT c From Customer c where c.home.city IN(:city)

The fix changes the parse tree node InNode and removes the special
handling of input parameter. Now the InNode passes an array of
Expression instances to the backend instead of a Vector of constant
values. I added two methods to the Expression class: in and notIn both
taking an array of Expression instances.

Thanks!

Regards Michael