ADF Component id and clientId

When we drag a ADF component to a page, ADF will generate an id like below:

<af:inputText id="it1" />

The id attribute rendered in the browser is obviously not the same as the value set in the ADF apge. This new id is the clientId and is produced by the UIComponent.getClientId(FacesContext) method.

public String getClientId(String componentId) {
    FacesContext context = FacesContext.getCurrentInstance();
    UIViewRoot root = context.getViewRoot();    
    UIComponent c = findComponent(root, componentId);
    return c.getClientId(context);
}

One good example of using client id is to display error message on a specific field.
The field will has a red border and mouse over to see the error message.
    
public static void displayMessage(Severity messageType,
                                      String messageTitle, String messageText,
                                      String componentId) {
        String clientId = null;
        if (componentId != null) {
            clientId = getClientId(componentId);
        }
        FacesContext fc = FacesContext.getCurrentInstance();
        FacesMessage message = new FacesMessage(messageTitle, messageText);
        message.setSeverity(messageType);
        fc.addMessage(clientId, message);

}

How to write CSS class in ADF

Following is an example of write CSS class. The advantage of using CSS class is to apply style to a specific component and do not affect the same component on other pages.

1. .yourClassName af|inputFile:update::content span:first-of-type {   
2.     max-width: 230px;   
3.     display: inline-block;   
4.     overflow: hidden;   
5.     text-overflow: ellipsis;   
6. } 

RowSetIterator next never returns null, causing infinite loop

The recommended way of using "RowSetIterator" for a view object:

Always create a "Secondary Row Set Iterator" and close it when finished.

Do not use getRowSetIterator() as it impacts row currency on the front end so firstly you should use createRowSetIterator and you should call closeRowSetIterator on the iterator created through this because if you don't, framework will create new ViewRowSetIteratorImpl instances and keep on adding them.

Code example:

DCBindingContainer bc = (DCBindingContainer)BindingContext.getCurrent().getCurrentBindingsEntry();

EmpVOImpl empVoImpl=(EmpVOImpl)bc.findIteratorBinding("EmpVO1Iterator").getViewObject();

    

RowSetIterator it = empVoImpl.createRowSetIterator(null);

while(it.hasNext()){

    EmpVORowImpl row=(EmpVORowImpl)it.next();

    if(row.getSal()!=null){

        totalAmount=row.getSal().add(totalAmount);

    }

}

it.closeRowSetIterator();

If necessary, use finally block

           try{
               while(it.hasNext()){

            EmpVORowImpl row=(EmpVORowImpl)it.next();

            if(row.getSal()!=null){ 

                  totalAmount=row.getSal().add(totalAmount);

            }

        }

} catch(Exception e) {

              //handle here

} finally {
      it.closeRowSetIterator();
}

Please refer to the links below for the issue:
https://community.oracle.com/thread/2242010
http://ramannanda.blogspot.ca/2013/04/adf-examining-memory-leaks.html
http://adfbugs.blogspot.ca/2009/07/iterating-through-view-object.html

https://community.oracle.com/message/12788828#12788828