Well, I've found the solution by myself
In case anyone runs into a problem like this, there goes the solution:
ejb-ql, by default, uses Unicode as its standard
string format, so there's no problem in passing or returning Unicode formatted strings, as I first thought.
The problem was in what I was **passing** as a parameter to the finder: I was calling the .findByServiceName(String) from a
Struts action that, surprisingly, didn't return me the html "post" parameters as Unicode (even though I had specified that the originating page had Content-Type="UTF-8").
So the solution was easy: prior to getting the "post" parameters, just the following call was needed:
request.setCharacterEncoding("UTF-8");
And now it works perfect
Thanks anyway for reading the post. See you
!
