Skip to main content

LOV problem in a multi line edit list

JDeveloper 11.1.2.1

We where having problems with our LOV lookups in a multi table edit list.

Where scolling down on the lov with a substantial number of records the LOV list would just reflect Fetching Records... indefinitely.

For now I have bound the multi list LOV to another lov model I had on the page with the same LOV in and it works but I will put some more time in finding another solution to this at some time because I am going on holiday next week - awesome.

Example
Had the following LOV on the page

<af:inputListOfValues id="ilov1" popupTitle="Search and Select: #{bindings.EmployeeId.hints.label}"
  value="#{bindings.EmployeeId.inputValue}"
  label="#{bindings.EmployeeId.hints.label}"
  model="#{bindings.EmployeeId.listOfValuesModel}"
  required="#{bindings.EmployeeId.hints.mandatory}"
  columns="#{bindings.EmployeeId.hints.displayWidth}"
  shortDesc="#{bindings.EmployeeId.hints.tooltip}">
  <f:validator binding="#{bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false" pattern="#{bindings.EmployeeId.format}"/>
</af:inputListOfValues>

And this LOV was the problematic on in an editable table.

<af:inputListOfValues id="employeeIdId"
 popupTitle="Search and Select: #{bindings.JobHistoryView1.hints.EmployeeId.label}"
 value="#{row.bindings.EmployeeId.inputValue}"
 model="#{row.bindings.EmployeeId.listOfValuesModel}"
 required="#{bindings.JobHistoryView1.hints.EmployeeId.mandatory}"
 columns="#{bindings.JobHistoryView1.hints.EmployeeId.displayWidth}"
 shortDesc="#{bindings.JobHistoryView1.hints.EmployeeId.tooltip}">
  <f:validator binding="#{row.bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false"
    pattern="#{bindings.JobHistoryView1.hints.EmployeeId.format}"/>
</af:inputListOfValues>

So I endeded up with this for the problematic one:
<af:inputListOfValues id="employeeIdId"
 popupTitle="Search and Select: #{bindings.JobHistoryView1.hints.EmployeeId.label}"
 value="#{row.bindings.EmployeeId.inputValue}"
 model="#{bindings.EmployeeId.listOfValuesModel}"
 required="#{bindings.JobHistoryView1.hints.EmployeeId.mandatory}"
 columns="#{bindings.JobHistoryView1.hints.EmployeeId.displayWidth}"
 shortDesc="#{bindings.JobHistoryView1.hints.EmployeeId.tooltip}">
  <f:validator binding="#{row.bindings.EmployeeId.validator}"/>
  <af:convertNumber groupingUsed="false"
    pattern="#{bindings.JobHistoryView1.hints.EmployeeId.format}"/>
</af:inputListOfValues>

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

ADF sort of generic screen for tables with the same structure

We have a couple (about a hundred) of tables with the same structure (Code, Description, Create Date, Update Date). So I wanted to do something simple so that I did not have to create all these screens 1) EO   I created the EO based on one of the tables I had that had the above columns. I then Added a transient attribute called table name to my EO based on a groovy expression. (the expression needs to change as I am reading web tier stuff from the model layer but I will fix this later) I then generated a java class for my EO. And added the following overriden method to my newly created java class. protected StringBuffer buildDMLStatement(int i, AttributeDefImpl[] attributeDefImpl,   AttributeDefImpl[] attributeDefImpl2, AttributeDefImpl[] attributeDefImpl3, boolean b) {   StringBuffer statement = super.buildDMLStatement(   i, attributeDefImpl, attributeDefImpl2, attributeDefImpl3, b); return new StringBuffer(StringUtils.replace(statement.to...
Post a Comment
Read more

Util code

public static MethodExpression getMethodExpression( String expr, Class returnType, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); ExpressionFactory elFactory = fc.getApplication().getExpressionFactory(); return elFactory.createMethodExpression( elctx, expr, returnType, argTypes); } public static javax.faces.el.MethodBinding getMethodBinding( String expr, Class[] argTypes){ FacesContext fc = FacesContext.getCurrentInstance(); ELContext elctx = fc.getELContext(); return fc.getApplication().createMethodBinding(expr, argTypes); } SetPropertyListener listener = new SetPropertyListener( ActionEvent.class.getName()); listener.setFrom(link.getRoute()); listener.setValueExpression("to", JSFUtils.getValueExpression("#{pageFlowScope.route}", String.class)); action.addActionListener(listener); AdfFacesContext.getCurrentInstance().getPageFlowScope() .put("route", lin...
Post a Comment
Read more

MANIFEST.MF merge JDeveloper for an executable jar

Goto your project > properties. Then click on deployment in the menu. Edit or add a jar deployment profile. Fill in the details under jar options (select Include manifest and give it a main class name) Also remember that the merge functionality only works with a BLANK line at the end of the merge file. REALLY this caught me. My merge file contents: Class-Path: commons-codec-1.3.jar [...empty line here CRLF...]
1 comment
Read more