Seam 2.1.1 EntityQuery problem after upgrade

phantom Feb 18, 2009 11:51 AM

Hi!

In my project I have a lot of defined in components.xml entity queries like this:

select object(a) from Article a where a.author = #{currentUser}

(CurrentUser is entity.)

In 2.0.2 such queries work correctly. But in 2.1.1 this doesn't work because instead of entity inserted result of toString() of my entity. So I should rewrite all my queries in such way:

select object(a) from Article a where a.author.userId=#{currentUser.userId}

Is there some more simple way to have the required back compatibility in EntityQuery?

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.
Actions
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:)
Actions
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.
Actions
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...
Actions

Go to original post