Validator in oracle ADF, Using af:attribute to make validation easy.

Hello all,

This post I will try to focus on how we can make validations in an editable table more effectively.

So what would we do if we have two attributes in a row in a table and we need to validate one on the basis of the other?

The answer is simple.

• We will get the instance of the viewObject 
• Then get the current row 
• Then we will get the attribute with which we need to compare and then we will compare and check the validation.

This process is fine, but i have a more easy and effective way to do so.

I have created a Transient attribute in EmployeeVO where the newSalary of the Employee is to be entered. We have to make sure that the new Salary is greater than old salary.

Drag the EmployeeVO into the page. Then add an af:attribute component in the inputText of newSalaryTrans . Give attribute name and a value here i have used 'oldSal' and assigned with value of old Salary i.e. #{row.Salary}.

Now we need to implement the validation and for that I created a Validator on the NewSalaryTrans field.

In the bean I have used the code given below :

    public void newSalaryVAL(FacesContext facesContext, UIComponent uIComponent, Object object) {
        Object val = uIComponent.getAttributes().get("oldSal");
        System.out.println("New Sal is  : "+object+" Old Sal is  : "+val);
        if(val != null){
            BigDecimal oldVal = (BigDecimal)val;
            BigDecimal newVal = (BigDecimal)object;
             if(oldVal.compareTo(newVal) >=0 ){
                throw new ValidatorException(new FacesMessage("New Salary Cannnot be less than Old Salary!"));
            }
        }
    }

On putting less value in newSalaryTrans

Here is the sample example : NewValidatorTestApp

Following the MVC Architecture in ADF, AMImpl method Called in Managed Bean

Hello everyone,

Here am about to explain how we can optimize our application for performance in ADF. ADF follows MVC architecture for application development.So there are times when we need an instance of model impl classes in the bean such as for example: we need AppModuleImpl in our bean class to get or fetch value from a view object. So for that we have to create an AppModuleImpl instance in the bean and then get viewObject from that.

So, if we get the AppModuleImpl object in bean then the purpose of MVC is being violated.I mean then we would be merging the model and viewController separation. And further more new instances of AppModuleImpl and etc, will created in our Managed Bean, this adds to violation of MVC Architecture . So it is better to keep the database logic in the database layer i.e. model and keep the controller logic in in viewController.

So the problem is that if we have to interact with the model layer from the bean, then how shall we do it?

The answer to this question is the use of ADF bindings.

Binding is used to interact with model layer from the viewController layer.

Suppose in a scenario, just for example we have to get the location of the employee by using EmployeeId. This needs interaction with the model layer.

So to do that we have to create a method that will take EmployeeId as input and give back location in return. 

1. Go to the AppModuleImpl and create a method.
   
   **Please do not use "Object" type in return parameter or in inputParameter,if you do this then the method will not be shown in ClientInterface**

       public Integer getLoc(Integer EmpId){
           Integer sal = null;
           Row[] row_2 = this.getEmployee1().getFilteredRows("EmployeeId", EmpId);
           if(row_2.length>0){
               sal = Integer.parseInt(row_2[0].getAttribute("Salary").toString());
           }
           return sal;
       }
   




2. Then go to clientInterface of the AM and add the method to clientInterface.
   
   
   
   
   
   
   
   
3. Then you have to create binding for this method on the page.
   
   
   
   
   
   
   
   
   
4. Now we have to call this binding and put the parameters in it from the bean.
   

       public void fetchSalary(ActionEvent actionEvent) {
           OperationBinding binding = getBindings().getOperationBinding("getLoc");
           // to put parameters value in the method
           binding.getParamsMap().put("EmpId", empId);
           Object execute = binding.execute();
           salary  = (Integer) execute;
       }
   

5. Now when you run the application.
   
   
   
   
   and when Fetch Salary button is clicked
   
   
6. You can download the sample application here : MethodBindingApp.rar.
7. If you have any query regarding this, please write in the comments.