[ http://jira.jboss.com/jira/browse/JBSEAM-1065?page=comments#action_12367453 ] Rob H. commented on JBSEAM-1065: -------------------------------- uhm? So just do it! override the getEjbl() and create your query by urself with ur restriction, watch the src code and do it like this. For me its working perfectly without JSF ValueBinding. Its not a BUG its a NEW FEATURE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1065?page=all ] Norman Richards updated JBSEAM-1065: ------------------------------------ Fix Version/s: 2.1.0.GA (was: 2.1.0.A1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1065?page=all ] Pete Muir updated JBSEAM-1065: ------------------------------ Fix Version/s: 2.1.0.BETA1 (was: 2.1.0.GA) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-1065?page=com.atlassian.jira.pl... ] Terry commented on JBSEAM-1065: ------------------------------- This issues has become a painful and pretty much a show stopper for me. please please enhance EntityQuery to support multiple value bindings on restriction. My scenario requires to build restrictions based on option user selects on the search page. Im in a situation, that if I do away with restrictions and use overridden getEjbql() method, then my query runs multiple times. But if I use restrictions then I have multiple binding error. All this can be resolved if this JIRA is resolved. I have provided some of my code below and attached screenshot of information. I have base EJBQL based on 5 tables: ----------------------------------- BASE_EJBQL = "select new " + CourseSysCourseListStore.class.getName() + "(c.id, c.code, c.shortDescription, " + "c.longDescription, c.descriptionMajorAreasOfStudy, c.keywords, " + "c.mosFullTime, c.mosPartTime, c.mosExternal, " + "o.id, o.shortName, oc.id, oc.shortDescription, " + "aos.id, aos.deetCode, aos.description, courseStatus.id) " + "from " + "CourseSysCourse c " + "join c.courseSysCourseOrganisationCampus oc " + "join oc.organisation o " + "join c.areaOfStudy aos " + "join c.courseStatus courseStatus"; ***Then I have about 8 simple restrictions, like this which work fine of course: restrictions.add("lower(o.id) like #{courseSysCourseList.selectedOrgIdConverted}"); ... ***But I also have several sets of restrictions like below, which need to be created and added based on search option selected by user on search ceritera page. These create problem: restrictions.add("(" + "lower(c.shortDescription) like concat('%',#{courseSysCourseList.freeTextSearchConverted},'%') or " + "lower(c.longDescription) like concat('%',#{courseSysCourseList.freeTextSearchConverted},'%') or " + "lower(c.descriptionMajorAreasOfStudy) like concat('%',#{courseSysCourseList.freeTextSearchConverted},'%') or " + "lower(c.keywords) like concat('%',#{courseSysCourseList.freeTextSearchConverted},'%')" + ")"); -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-1065?page=com.atlassian.jira.pl... ] Shane Bryzak updated JBSEAM-1065: --------------------------------- Fix Version/s: 2.1.1.CR1 (was: The future) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-1065?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-1065: ------------------------------ Assignee: (was: Pete Muir) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-1065?page=com.atlassian.jira.pl... ] Shane Bryzak updated JBSEAM-1065: --------------------------------- Fix Version/s: 2.1.2.CR1 (was: 2.1.1.CR2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBSEAM-1065?page=com.atlassian.jira.plugi... ] Karsten Wutzke commented on JBSEAM-1065: ---------------------------------------- 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 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira