ADF BC Attribute with VC of CONTAINS Ignores Choice List on the LOV

Question

JDev 11g PS 1.
Objects:
- A view criteria with attribute defined as CONTAINS (literal)
- An LOV on that attribute with a default list type UI hint of Choice List
- ADF Faces query-table based in the VC
Problem: query-table ignores the Choice List and renders an Input Text.
Clue: Changing the operator to EQUALS causes the expected Choice List to be rendered in ADF BC.
If this is documented in the online help or in this forum, it is escaping me.
Anyone know the best workaround? Set the VC using EQUALS and switch it to CONTAINS in buildWhereClause() maybe?
Thanks,
Peter

Answer 1

Frank,
Thanks for the fast reply and for the bug entry. Unfortunately stopping work is not an option. We've come up with a solution using a query listener that replaces EQUALS with CONTAINS before the query and resets it to EQUALS after the query (otherwise the component draws the text item after the query).
Maybe you can think of another solution to our requirement: display a single master record in the results table for a master-detail database view. For example, in an altered Oracle HR world, each DEPARTMENTS record is associated with multiple LOCATIONS records (through a DEPT_LOC table). A database view, DEPT_LOC_VW, based on that table also contains the location description and department description.
Users want to select and then edit (on another page) a department by querying by location. If we represent DEPT_LOC_VW in the query-table component, we see multiple result rows for a single department and that is unnecessary confusion for the purpose of editing a single department.
So we have created an alternative database view, DEPT_VW, based on DEPARTMENTS only, with an additional column -- LOC_LIST -- based on a function that returns a delimited list of all location codes for that department. This way, the user sees only one department record in the results table (although we lose the location description in the results -- not an issue) and is still able to query based on location.
A LOCATIONS_VW view contains the location code surrounded with the delimiiter. The DeptVw view attribute LocList contains an LOV based on that database view.
We want the view criteria to create a query condition:
WHERE loc_list LIKE '%'||<selected location code>||'%'We thought about some kind of clever use of a subquery using a bind variable:
SELECT...
FROM  departments -- not DEPT_VW or DEPT_LOC_VW
WHERE department_id IN (
   SELECT department_id
   FROM   dept_loc
   WHERE  location_id = NVL(:userSelectedLocationId, location_id);But that bind variable does not show in the view criteria selection list so it will not appear in the query component.
Thanks again,
Peter