Different LOVs for a single attribute?

Question

Hi,
In our application, we use a "domainvalues" table to store all valid values for enumerated fields. The table has a typical design, with the domain name and the value as primary key and a field for the description. In the database this table is used to validate those enumerated fields. In our ADF GUI we use this table to fill single select lists. For each domain we have a read only View Object, which has a query like this:select value
,      description_short
from   domainvalues
where  upper(dmn_name) = 'IND_YES_NO'
ORDER BY description_shortNow we have a domain with three values, of which one value should not be used under certain circumstances. We simply created two domains, resulting in our domainvalues table containing (among others) the following rows:dmn_name  value  description_short
dom1          1  one
dom1          2  two
dom1          3  three
dom2          1  one
dom2          3  threeNow we have an Entity Object-based View Object that should use one of these lists. Which list is used depends on the page in which the View Object is used. So I selected the appropriate attribute in the View Object editor. Under "List of values" at the bottom of the screen I clicked the green + button to add a List of Values. I added an LOV with the following settings:
<ul><li>Name = LOV_Domain1
<li>List data source = Domain1ViewObject
<li>List attribute = value</ul>
The I added a second LOV by clicking the green + again. This time I used this settings:
<ul><li>Name = LOV_Domain2
<li>List data source = Domain2ViewObject
<li>List attribute = value</ul>
After creating the second LOV, a column of radio buttons appears in front of the table of LOVs, allowing me to select a default. The Domain1 LOV is selected as default and I keep it that way.
Now when I drag-and-drop the field on a page and choose to add it to the page as an "ADF Select One Choice", a List Binding is created in my page definition file. If I double click that list binding, the Edit List Binding dialog opens. the "Model Driven List" option is selected and I am able to select a Base Data Source Attribute and a Server List Binding Name. The Server List Binding Name option is where I am able to select which LOV provider I want to use. In this case I want to use "LOV_Domain2", the one that lacks the value 2. So I selected that one from the list, instead of the default selected "LOV_Domain1". So far so good.
The problem is, when I run the page, my select list still contains all three values, so I have the impression that the default LOV is used, regardless what is selected in the page definition. Is this a bug, or am I missing something?
Best regards,
Bart Kummel

Answer 1

Okay, I've figured out a work around myself. I just added an extra attribute in the View Object, based on the same attribute in the Entity Object. Each attribute of the View Object has it's own LOV definition. I only have to select the other attribute in my JSP to get the other LOV. I still think the solution with two LOV definitions associated with a single attribute would be more elegant. I hope this will be added in a next version.
Best regards,
Bart Kummel