Best pratice on disabling fields?

Question

Hi,
   I'm using jdev11R1. I'm having one jspx page named(firstpage.jspx). this page is on unboundedTF.
I want to disable more than 15 fields on a single hit of button. but here each and every developer has different approach to do this.
can any one of the expert says which one is best approach?
Developer 1 Approach:
1. saying that bind the all fields in your bean.
2. Inside button actionlistener bindvar.setDisabled(true).
2. add partial target programmatically.
Developer1 saying his Advantage on his view:
1. ADF traditionally Approach (create bindings). Apart from that i no need to any other stuff
Developer 2 Approach:
1.  I'll create 15 variable in your bean return type should Boolean along with getter setter.
2.  i'll have a common method public void endis(Boolean bool) {this.setVar(bool);}
3.  Inside button actionlistener i'll call endis(true);
4. add partial target programmatically.
5. last step in all fields i have to use el expersion like #{scopetype.beanname,var}
Developer2 saying his Advantage on his view:
1. Java traditionally Approach(getter setter).
2. In future if i there is a change in requirement like
    - no need to disable all the fields. just some fields.
    - repeat same thing some other buttons.
    ultimately no need to re-write fully .little bit effort only needed.
Developer 3 Approach :
1. I have a pageFlowScope variable inside the actionlistener AdfFacesContext.getCurrentInstace.getPageflowScope.put('disable','y');
2. go to all fields have el expression like #{pageFlowScope.disable eq 'y' ? true : false}
Developer3 saying his Advantage on his view:
1. No need of binding and no need of variable declaration, getter and setter in bean. just piece of code
Developer1 perspective saying that following:
   --Developer2 doing having lot of code for disabling the fields.
   --Developer3 not best approach. because oracle docs saying that pageflowscope only for BTF. But pageflowscope works in unboundedTF also.
Developer2 perspective saying that following
  --Developer1 binding the each and every variable into the bean for disabling the fields. default binding take care of framework why should i do?
  --Developer3 anyhow it will create getter and setter for that by the framework. if scope value lost all will fails.
Developer3 perspective saying that following
  --Developer1 binding the each and every variable into the bean for disabling the fields. default binding take care of framework why should i do?
  --Developer2 having lot of code for disabling the fields.
"from the bottom line of developer discussion i conclude.
each and every one saying I'm the best. but each and every approach has own strength and weakness."
My question will be
1.Is there any other approach apart from these three?
before answering the second question. have these things in mind.
   point1. simple and re-usable all developer.
   point2. resource usage(memory allocation).
   point3. less time to do this job. here after.
2.please suggest which Best Approach in all of the prespective?
-edited lately, please go through again,
thanks,

Answer 1

Developer 1 Approach:
Developer1 saying his Advantage on his view:
1. ADF traditionally Approach (create bindings).
Since when is this the traditional approach? Never bind components to a bean if it's not really necessary! As you have other solutions this one is out of the race.
Developer 2 Approach:
Developer2 saying his Advantage on his view:
1. Java traditionally Approach(getter setter).
2. In future if i there is a change in requirement like
    - no need to disable all the fields. just some fields.
    - repeat same thing some other buttons.
    ultimately no need to re-write fully .little bit effort only needed.
Yes, but how likely is it that you have to change the fields to enable/disable?
From my point of view you put in a lot of effort for something you don't know if it will happen at all. Even if you know it's coming it would be easier to build groups and use the group variable to enable/disable the fields. You can then change a field from group a to group b without much programming.
Developer 3 Approach :
Developer3 saying his Advantage on his view:
1. No need of binding and no need of variable declaration, getter and setter in bean. just piece of code
You don't even need the code in the actionListener as you can use a setPropertyListener for this. The question here is why putting the variable into page flow scope? We don't know the use case to answer this. Generally you should not put anything in pageFlowScope if it's not needed outside the page. This we don't know. PageFlowScope is a broad scope, so you should think about using a smaller scope if possible.
4. Solution: put all the fields into one layout container. Write a method in a bean method to which enables/disables all input Fields of a given container Something like this
    // toggle disable of all the child uicomponents inside the given uiComponent
    private void toggleDisableInputItems(AdfFacesContext adfFacesContext, UIComponent component) {
        List<UIComponent> items = component.getChildren();
        for (UIComponent item : items) {
            toggleDisableInputItems(adfFacesContext, item);
            if (item instanceof RichInputText) {
                RichInputText input = (RichInputText) item;
                input.setDisabled(!input.isAutoSubmit());
                adfFacesContext.addPartialTarget(input);
            } else if (item instanceof RichInputDate) {
                RichInputDate input = (RichInputDate) item;
                input.setDisabled(!input.isAutoSubmit());
                adfFacesContext.addPartialTarget(input);
There are probably more solutions. I would stick with 3 or 4 depending on the use case.
Timo