[
https://issues.jboss.org/browse/JBSEAM-1065?page=com.atlassian.jira.plugi...
]
Karsten Wutzke edited comment on JBSEAM-1065 at 12/13/10 10:42 AM:
-------------------------------------------------------------------
I have a JPQL statement where I need to join a table/entity twice, which causes the
restrictions
scf.roster.id = ro.id AND sca.roster.id <> ro.id
In Seam FW this would be
lsRestrictions.add("scf.roster.id = ro.id");
lsRestrictions.add("sca.roster.id <> ro.id");
I can't replace it via EL, why is this only a MINOR bug and why is it a FEATURE?
was (Author: kwutzke):
I have a JPQL statement where I need to join a table/entity twice, which causes the
restrictions
scf.roster.id = ro.id AND sca.roster.id <> ro.id
In Seam FW this would be
Entity Query should support multiple value bindings on restrictions.
--------------------------------------------------------------------
Key: JBSEAM-1065
URL:
https://issues.jboss.org/browse/JBSEAM-1065
Project: Seam
Issue Type: Feature Request
Components: Framework
Affects Versions: 1.2.0.GA
Reporter: sal something
Priority: Minor
Labels: patch
Fix For: The future
Attachments: patch.txt, screenshot-1.jpg
Entity Query should support multiple value bindings on restrictions.
The use case would be the 'between' statement, as of now Entity Query will throw
an exception using a 'between' statement:
Caused by: java.lang.IllegalArgumentException: there should be exactly one value binding
in a restriction: applicationDeadline between #{vacancyBrowseSearch.appDeadlineStartDate}
and #{vacancyBrowseSearch.appDeadlineEndDate}
at org.jboss.seam.framework.Query.parseEjbql(Query.java:145)
at org.jboss.seam.framework.EntityQuery.createQuery(EntityQuery.java:100)
at org.jboss.seam.framework.EntityQuery.getResultList(EntityQuery.java:41)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira