This content has been marked as final.
Show 4 replies
-
1. Re: Seam 2.1.1 EntityQuery problem after upgrade
blabno Feb 18, 2009 1:05 PM (in response to phantom)It should work the first way too. If not this is a bug.
-
2. Re: Seam 2.1.1 EntityQuery problem after upgrade
phantom Feb 18, 2009 2:44 PM (in response to phantom)Yes, I think so too - but it doesn't work for me:)
Please someone check this problem. If it realy exists - I think it should be fixed:) -
3. Re: Seam 2.1.1 EntityQuery problem after upgrade
nicolas.bielza Feb 18, 2009 3:32 PM (in response to phantom)We too would like to see this problem fixed.
Rewriting the queries isn't really a solution: you'll need put quotes around expressions that return a String and escape them in the String itself.
That same problem was mentioned before but to my knowledge it has not been addressed yet.
-
4. Re: Seam 2.1.1 EntityQuery problem after upgrade
phantom Feb 19, 2009 12:10 PM (in response to phantom)It seems to me that in Seam 2.1.1 EntityQuery.setEjbql have been invoked with already converted
#{...}
. So - EntityQuery recieve just text - and don't perform any substitution. As a result - the problem lies somewhere else - not in EntityQuery: but in algorithm wich instantiate entities from XML components.xml...