Connecting the {Dots}

Oracle ADF helps you to build af:query component declaratively by dropping view criteria defined in a view object on to a page. While building view criteria you can create custom operators or remove built-in operators (displayed in advanced mode of af:query component) for each view criteria item by adding <CompOper/> to the view object XML file. Note that you may need to do it manually, there is no editor support for the same. This concept is explained in developers guide under the topic - How to Create Custom Operators or Remove Standard Operators . The attributes used in <CompOper/> as as follows: Name: Specify an id for the operation. ToDo: Set to 1 to add this custom operator. Set to -1 to remove an operator. OperDescStrCode: Specify the id used in the message bundle to map to the description string. Oper: Set to a value that will be used programmatically to denote this operation in the SQL statement.  MinCardinality: If there is an input r...

Following example illustrates how to disable UI component using ADF Faces Java Script API. This example disables  af:inputText when you click the button. Note that af:inputText has set unsecure="disabled" and clientComponent="true". You must set these properties appropriately to  set component properties in the client side.  unsecure   A whitespace separated list of attributes whose values ordinarily can be set only on the server, but need to be settable on the client. Currently, this is supported only for the "disabled" attribute. Note that when you are able to set a property on the client, you will be allowed to by using the the .setProperty('attribute', newValue) method, but not the .setXXXAttribute(newValue) method. For example, if you have unsecure="disabled", then on the client you can use the method .setProperty('disabled', false), while the method .setDisabled(false) will not work and will provide a javascript e...