Oracle Forms allowed developers to associate a smart list of values with an inputtext field. The intelligence of the Forms LOV appears almost mind reading in that it doesn’t pop up the LOV if the partial search condition entered by the user retrieves a single match only. If more than a single match is returned, a LOV dialog is opened with the pre-fetched list of data. Of course, Oracle Forms LOV can also be used the dumb way, in which the user hits the LOV button to then manually enter the query condition before pressing the execute query button. In JDeveloper 11, the ADF Faces and ADF development teams have closed the gap that existed in 10.1.3 for LOV on the web. A new component, the af:inputListOfValues component, is introduced that, in combination with ADF Business Component’s model driven list of values, can be configured to behave and act like LOVs in Oracle Forms. This how-to document shows and explains how to build such a list of values and also unveils the little code to write to make the LOV pre-fetching a list of values based on the partial user input in the input text field.

how to build a simple EJB3/JAX-WS/JAXB web service contract first

a small code snippet on how to avoid selection-state reset of an ADF table when the underlying method is re-queried

In JDeveloper 11, JavaScript events like onClick, onFocus etc. are handled through the ADF Faces RC client framework using the af:clientListener component. The signature of the af:clientListener is defined such that the developer provides the name of a method to call and the JavaScript event to trigger this method call. The clientListener signature however doesn't foresee a mechanism for the developer to pass additional arguments - like a rowKey - to the JavaScript method. Here client attributes come to the rescue.