Disable - command button

We use jdeveloper 11.1.1.3
In a jspx page, I need to show a "save" commandbutton disabled to start with.
After the data is queried (inputtextfield1 gets shown) I need to show the "save" button enabled so that user can click.
That enabling is to be based on the inputtextfield1 value being not null.
How do I do this please.
Thanks for your help.

Here is the syntax:
<af:form id="f1">
<af:inputText label="Label 1" id="it1" binding="#{TestPageBean.myInputText}"/>
</af:form>
Bean Code:
import oracle.adf.view.rich.component.rich.input.RichInputText;
public class TestPageBean {
private RichInputText myInputText;
public TestPageBean() {
public void setMyInputText(RichInputText myInputText) {
this.myInputText = myInputText;
public RichInputText getMyInputText() {
return myInputText;
*public boolean checkIfEmpty() {*
*if (this.myInputText != null) {*
*if (this.myInputText.getValue() == null) {*
return true;
return false;
I am NOT clear with your use-case. Can you please clearly specify?
Thanks,
Navaneeth

Similar Messages

  • JDev 10 - disable command button depending on which row is selected

    I am using JDeveloper 10, and I have a table which has some data columns and a selection facet with View and Edit command buttons.
    I would like all rows to be viewable. When you click the view event it goes to another .jsp with the view action.
    It does the same thing with the edit action, however I would like to only allow rows which have an EffectiveDate column in the future to be editable.
    Is there some way to disable the edit button when those rows are selected, or to throw a validation error when the edit button is clicked for that row?
    Thanks!
    Jeff
              <af:table value="#{bindings.RateList.collectionModel}" var="row"
                          rows="#{bindings.RateList.rangeSize}"
                          first="#{bindings.RateList.rangeStart}"
                          emptyText="#{bindings.RateList.viewable ? 'No rows yet.' : 'Access Denied.'}"
                          selectionListener="#{bindings.RateList.collectionModel.makeCurrent}"
                          selectionState="#{bindings.RateList.collectionModel.selectedRow}">
                  <af:column sortProperty="RateType" sortable="false"
                             headerText="#{bindings.RateList.labels.RateType}">
                    <af:outputText value="#{row.RateDescription}"/>
                  </af:column>
                  <af:column sortProperty="EffectiveDate" sortable="false"
                             headerText="#{bindings.RateList.labels.EffectiveDate}">
                    <af:outputText value="#{row.EffectiveDate}">
                      <f:convertDateTime pattern="dd-MMM-yyyy"/>
                    </af:outputText>
                  </af:column>
                  <f:facet name="selection">
                    <af:tableSelectOne text="Select and">
                      <af:commandButton text="View" action="view">
                        <af:setActionListener from="#{row.rowKeyStr}"
                                              to="#{requestScope.requestRowKey}"/>
                      </af:commandButton>
                      <af:commandButton text="Edit"
                                        action="edit"/>
                    </af:tableSelectOne>
                  </f:facet>
                </af:table>

    So, I first tried using Chan advice, I added a new editable property from the database and then added Edit buttons to each row in the table with disabled property set to the editable property.
    This correctly displayed buttons which were editable in the correct rows.
    However, I was no longer using the select functionality which passed the rowId of the selected row to the edit page.
    I wasn't able to quickly solve this problem so I tried John's solution.
    I feel really dumb, but after about 20 rereadings it was still completely Greek to me, I have no idea what he was recommending.
    So I added onclick="return editTest()" to the Edit button.
    The I added ID to the relevant locations, and the following javascript to the page, and this is working well enough now.
    (Oh, I display the date in a slightly odd dd-MMM-yyyy format, due to slightly odd customer requirements.)
    I've probably misspelled one of the months, haven't yet finished testing.
    A couple of gotchas I found
    - Do not add onclick="editTest()" or else it will continue processing and allow all rows to be edited.
    - Putting date = document.getElementById('mainFormId:tableId:'+i+':EffectiveDateId'); would work for the original search,
    but after filtering results i and found_it are not equivalent, and date was not found in the page.
               function editTest(){
                  var found_it;
                  var date;
                  for (var i=0; i < document.getElementsByName('mainFormId:tableId:selected').length; i++)  {
                     if (document.getElementsByName('mainFormId:tableId:selected').checked) {               
    found_it = document.getElementsByName('mainFormId:tableId:selected')[i].value;
    date = document.getElementById('mainFormId:tableId:'+found_it+':EffectiveDateId');
    var result = date.innerHTML.split("-");
    var day = result[0];
    if (day.charAt(0) == '0'){
    day = day.charAt(1);
    var month;
    var monthTxt = result[1];
    switch (monthTxt) {
    case 'Jan':
    month=0;
    break;
    case 'Feb':
    month=1;
    break;
    case 'Mar':
    month=2;
    break;
    case 'Apr':
    month=3;
    break;
    case 'May':
    month=4;
    break;
    case 'Jun':
    month=5;
    break;
    case 'Jul':
    month=6;
    break;
    case 'Aug':
    month=7;
    break;
    case 'Sep':
    month=8;
    break;
    case 'Oct':
    month=9;
    break;
    case 'Nov':
    month=10;
    break;
    case 'Dec':
    month=11;
    break;
    default:
    month=11;
    break;
    var year = result[2];
    var today = new Date();
    var effDate = new Date();
    effDate.setDate(day);
    effDate.setMonth(month);
    effDate.setYear(year);
    if (effDate < today) {
    alert ('Sorry, you cannot change a rate with an effective date in the past');
    return false;
    } else {
    return true;

  • Command button remains disabled after a request redirect to a PDF Servlet

    Hi All,
    I've a command button to generate PDF on the fly and used to work in JDev 10.1.3.3.
    When we migrated to 11g, it works for the first time on a page, and the file Open/Save dialog will come up.
    But then the command button remains grayed out, and clicking doesn't generate a server call.
    If I do something on the page which does a partial or full submit, then the button will get enabled again.
    Any suggestions?
    Thanks,
    Jaimon
    Sample code:
    Facelets:
    <af:commandButton text="Create PDF" action="#{fs02.createPDF}" />
    Java:
    public String createPDF() {
    //Validation checks here. If there are any errors, it gets added to FacesMessages to display on the same page.
    if(!validate()) {
    //sf.addInfoMessage('message here..');
    }else {
    FacesContext ctx = FacesContext.getCurrentInstance();
    HttpServletRequest request = (HttpServletRequest)ctx.getExternalContext().getRequest();
    HttpServletResponse response = (HttpServletResponse)ctx.getExternalContext().getResponse();
    RequestDispatcher rd = request.getRequestDispatcher("/pdfdownloader");
    rd.forward(request, response);
    ctx.responseComplete();
    return null;
    pdfdownloader is mapped as a servlet, which writes the actual PDF content as a stream.

    Herewith the code which is triggered with the post-forms-commit trg. As far as I can see it, there is no code to disable/enable the save button in the menubar.
    ===
    PROCEDURE validate_enbr_records IS
    CURSOR c_enbr
    IS
    SELECT exlb.exlb_length
    , enbr.enbr_ind_break
    FROM dog_envelop_breaks enbr
    , dog_extrnl_labels exlb
    WHERE enbr_appl_cod = :flow_appl_cod
    AND enbr_flow_cod = :flow_cod
    AND enbr_sort_seqnr <> :enbr_sort_seqnr
    AND enbr_appl_cod = exlb_appl_cod
    AND enbr_exlb_cod = exlb_cod;
    CURSOR c_exlb
    IS
    SELECT exlb_length
    FROM dog_extrnl_labels
    WHERE exlb_appl_cod = :flow_appl_cod
    AND exlb_cod = :enbr_exlb_cod;
    l_lengte_break_label NUMBER := 0;
    l_lengte_sort_label NUMBER := 0;
    l_length NUMBER := 0;
    l_aant NUMBER := 0;
    r_enbr c_enbr%ROWTYPE;
    mi_id MenuItem;
    BEGIN
    FOR r_enbr in c_enbr LOOP
    IF r_enbr.enbr_ind_break = 'Y'
    THEN
    l_lengte_break_label := l_lengte_break_label + r_enbr.exlb_length;
    ELSE
    l_lengte_sort_label := l_lengte_sort_label + r_enbr.exlb_length;
    END IF;
    l_aant := l_aant + 1;
    END LOOP;
    OPEN c_exlb;
    FETCH c_exlb INTO l_length;
    CLOSE c_exlb;
    IF :enbr_ind_break = 'Y' THEN
    l_lengte_break_label := l_lengte_break_label + l_length;
    ELSE
    l_lengte_sort_label := l_lengte_sort_label + l_length;
    END IF;
    IF l_lengte_break_label > 48
    THEN
    qms$errors.show_message('DOG-10194');
    END IF;
    IF l_lengte_sort_label > 50
    THEN
    qms$errors.show_message('DOG-10195');
    --set_record_property(3,'enbr',status,changed_status);
    END IF;
    IF :system.record_status = 'CHANGED' THEN
    set_menu_item_property('FILE_MENU.SAVE',ENABLED,'YES');
    END IF;
    END;
    ===
    After the message has been throughn and the OK-button has been clicked, the code is never reaching the code:
    IF :system.record_status = 'CHANGED' THEN
    set_menu_item_property('FILE_MENU.SAVE',ENABLED,'YES');
    END IF;
    The save-button remains disabled.
    Best regards
    John.

  • Set JSF Command Button Disabled

    Hello,
    I have a JSF command button, I would like to dynamically change button disabled based on certain condition.
    I tried in the actionListener code in my managedbean
    like
    UIComponent component = event.getComponent();
    component.setRendered(false);However it makes button not visible, couldn't find setDisabled.
    How can I do this?
    Regards

    Hi,
    Basically, you can change the button status: enabled/didasled from JavaScript by changing the button css.
    You can also do this from JSF.
    The commandButton element has the disabled attribute and you can change the status depending on your condition.
    -- <h:commanButton disabled=""
    Please find an example: http://www.roseindia.net/jsf/EnableDisableButton.shtml
    If you use AJAX (ex. a4j) there is the same principle. In backing bean you can check your condition and in jsp you'll change to disabled.
    Hope this helps,
    Sergiu

  • How can I control the enable/disable of command buttons in ADF JSF

    I have been having a great deal of trouble trying to work out how to control the command button such that if the rowset is null then the button is disabled. The trick is that the rowset is not defined by the view where the command button is located. The rowset is defined by a view which has a "view" command button which displays the specific row selected, then this view has a command button that will display the detail rowset of the selected master row, but if there are no detail records I want the button to be disabled. How can I do this in ADF JSF? If I use a backing bean to make the determination prior to the page rendering then how does the backing mean method set the parameter necessary to disable the command button? Any advice or tutorial that I can use is most appreciated. My goal with using ADF JSF effort was to demonstrate that a complex app could be generated with minimum coding, I would like to keep to this concept if possible. Thanks,
    Michael

    Hi Michael,
    You can probably set the Enabled property of the command button using an EL that would evaluate and return true or false based on your requirement.
    Check out these links for more information on using the EL.
    http://radio.weblogs.com/0118231/2006/11/10.html
    http://database.in2p3.fr/doc/oracle/Oracle_Application_Server_10_Release_3/web.1013/b25947/web_dcp006.htm
    -Arun

  • Cannot completely disable a dimmed command button

    Hi! Everyone,
    I thought this topic was solved before, but it comes back to me again.
    Please take a look at the code in the attached project.
    If the call of "Delay(5)" is placed after "ProcessSystemEvents()" call in the A_Callback() function, B-LED always light up no matter what!? 
    Dimming or making button B invisible doesn't disable the command button at all. 
    Only when I place the "Delay(5)" call in front of the "ProcessSystemEvents()", the B button will be disabled.
    Just by dimming button B, without "ProcessDrawEvents()" and "ProcessSystemEvents()", won't guarantee the button is disabled.
    I'm puzzled.  What is the correct way of completely disable a command button?
    Does this problem only happen in CVI 6.0?
    Solved!
    Go to Solution.
    Attachments:
    DimButtons.zip ‏5 KB

    Whether or not you need to call ProcessSystemEvents to ignore clicks on a button depends on what you are doing at the time and when you will undim the control.  The original question came up when the button was being dimmed and undimmed in a callback.
    CVI defers processing of events while you are in a callback.  If you're not currently in a callback, a click event will be processed when it occurs.  If the control is dimmed when that click occurs, (again, outside of a callback), the event will be processed and ignored and you don't need ProcessSystemEvents.
    Or if you dim the control from within a callback, then click on the control, then exit the callback without undimming the control, the event will be processed with the control dimmed and will therefore be ignored (without needing ProcessSystemEvents).
    So the big question is when will you undim the control?  If you undim it at the end of a long callback, then you need to call ProcessSystemEvents.
    But if, for example, you open a panel with a control dimmed, and then undim it after some other event, you don't need ProcessSystemEvents to ignore the click.
    Let's say you have a panel with a control for the user to select a filename, and a button to print the selected file.  You don't want Print to be active until the file is selected, so it's dimmed initially by default.  In a callback for the filename control, after the user selects a file, you can then undim the Print button without needing to call ProcessSystemEvents.  Any click on the previously dimmed Print button will have already been ignored.

  • How to enable /disable a command Button based on a table's selectOne choice

    Hi everyone.
    I am using JDeveloper 10.1.3.3 and wish to enable / disable a commandButton based on the user's selection of the selectOne radio button.
    The idea is that a row of a table may have an associated document so I want to enable or disable the button that downloads it based n the current row selected.
    I have followed the advice on problem with table I defined my selectOne component as follows :
    <af:tableSelectOne text="#{res['tables.selectionFacet.title']}"
        autoSubmit="true"
        attributeChangeListener="#{backing_browseCVs.onSelectionChange}">The function inside the backing bean looks like this
        public void onSelectionChange(AttributeChangeEvent attributeChangeEvent)
            // access the faces context
            FacesContext fc = FacesContext.getCurrentInstance();
            // get value of the expression #{row.hasCVDocument} that indicates
            // if a document has been added
            ValueBinding vb =
                fc.getApplication().createValueBinding("#{row.hasCVDocument}");
            Boolean hasDoc = (Boolean)vb.getValue(fc);
            // enable the doownload button accordingly
            downloadCVDocBtn.setDisabled(!hasDoc);
        }My problem is that the method never fires. I have placed a breakpoint at the first line but it is never reached.
    Any advice will be most welcome.
    Thanassis

    Hi,
    You might need to add 'dataProvider' part in the expression language in your selectionListener:
    #{bindings.CVList.currentRow.[b]dataProvider.hasCVDocument}
    #{bindings.CVList.currentRow} returns an instance of ViewRowImpl which does not have 'getHasCVDocument()' method, but does have:
    Object getCurrentRow()
    method, which returns objects from your CVList list, which do have getHasCVDocument() method...
    Expression language is resolved through reflection, so when you write:
    #{processScope.someClass.someReferencedClass.someAttribute} it is something like:
    Get someClass from processScope map, then:
    someClass.getSomeReferencedClass().getSomeAttribute()
    It's a bit more complex but you get the idea.
    Vladimir

  • Disable Command Link (Button)

    From my backing Bean I would like to dynamically disable
    the buttons on my jsp form. How do you do it? I have tried as I
    would with fields but I get a failure.

    There is no "disabled" attribute for commandLink. Perhaps it would be ok if you just set the "rendered" attribute to false? Of course, that would eliminate the commandLink completely from the page.
    CowKing

  • Disable delete button in Table Maintainance Generator

    Hello all,
      How to disable delete button in Table maintainance generator???

    Hi Maya,
    It is very interesting question. If you debug your table maintenance screen, the program of table maintenance screen will not have statically defined pf status. So you cannot exclude delete functionalities using the below statement.
    SET PF-STATUS <the GUI status> EXCLUDING 'DELE'.
    For viewing pf status SAP has programmed in dynamic manner using this FM VIEW_SET_PF_STATUS.
    Before calling above FM you need to exclude delete function. Follow the following step for achieving this
    Go to sm30. Put your table name and press on maintain push button. It will display table entries in maintenance screen.
    Go to system->status
    Click on program name.
    Go to your flow logic of you table maintenance screen number.
    It will have following code in flow logic
    PROCESS BEFORE OUTPUT.
    MODULE LISTE_INITIALISIEREN.
    LOOP AT EXTRACT WITH CONTROL
      TCTRL_ZMAINTAIN CURSOR NEXTLINE.
       MODULE LISTE_SHOW_LISTE.
    ENDLOOP.
    PROCESS AFTER INPUT.
    MODULE LISTE_EXIT_COMMAND AT EXIT-COMMAND.
    MODULE LISTE_BEFORE_LOOP.
    LOOP AT EXTRACT.
       MODULE LISTE_INIT_WORKAREA.
       CHAIN.
        FIELD ZMAINTAIN-MATNR .
        FIELD ZMAINTAIN-KUNNR .
        FIELD ZMAINTAIN-LIFNR .
        MODULE SET_UPDATE_FLAG ON CHAIN-REQUEST.
       ENDCHAIN.
       FIELD VIM_MARKED MODULE LISTE_MARK_CHECKBOX.
       CHAIN.
        FIELD ZMAINTAIN-MATNR .
        MODULE LISTE_UPDATE_LISTE.
       ENDCHAIN.
    ENDLOOP.
    MODULE LISTE_AFTER_LOOP.
    Add new module in PBO for excluding delete function. ex  module set_pf.
    PROCESS BEFORE OUTPUT.
    ****here I added my own code for excluding delete function
    ****begin of addion
    module set_pf.
    ****end of addition
    MODULE LISTE_INITIALISIEREN.
    LOOP AT EXTRACT WITH CONTROL
      TCTRL_ZMAINTAIN CURSOR NEXTLINE.
       MODULE LISTE_SHOW_LISTE.
    ENDLOOP.
    PROCESS AFTER INPUT.
    MODULE LISTE_EXIT_COMMAND AT EXIT-COMMAND.
    MODULE LISTE_BEFORE_LOOP.
    LOOP AT EXTRACT.
       MODULE LISTE_INIT_WORKAREA.
       CHAIN.
        FIELD ZMAINTAIN-MATNR .
        FIELD ZMAINTAIN-KUNNR .
        FIELD ZMAINTAIN-LIFNR .
        MODULE SET_UPDATE_FLAG ON CHAIN-REQUEST.
       ENDCHAIN.
       FIELD VIM_MARKED MODULE LISTE_MARK_CHECKBOX.
       CHAIN.
        FIELD ZMAINTAIN-MATNR .
        MODULE LISTE_UPDATE_LISTE.
       ENDCHAIN.
    ENDLOOP.
    MODULE LISTE_AFTER_LOOP.
    *****inclule one line of code for excluding delete fucion
    module set_pf output.
          MOVE 'DELE' TO excl_cua_funct-function. COLLECT excl_cua_funct.
    endmodule.
    Basically sap fetching status dynamically from program SAPLSVIM using FM VIEW_SET_PF_STATUS. Status name is EULG.
    Please donu2019t hardcode anything by using set pf status statment, you just add one line of code the PBO by creating new module.
    Let me know if you need any help .
    Cheers.
    Regards,
    Peranandam

  • Command button does not commit unless hit twice

    I'm using ADF/BC, 10.1.3.2 jdev. I have the following code in my backing bean:
        public String cardLost() {
            inputText12.setValue("1"); 
            BindingContainer bindings = getBindings();
            OperationBinding operationBinding =
                bindings.getOperationBinding("Commit");
            Object result = operationBinding.execute();
            if (!operationBinding.getErrors().isEmpty()) {
                return null;
            return null;
    The command button is defined as follows:
    <af:commandButton
                                    text="Save" disabled="false"
                                    binding="#{find_student_mb.commandButton4}"
                                    id="commandButton4"
                                    action="#{find_student_mb.cardLost}"
                                    immediate="false"/>When I hit the Save button the first time, the input text field (inputText12) changes to 1, but the data does not get commited to the database. (I have verified this in the database) If I hit the Save button again, the data gets committed.
    Is there a way to update the field and commit the data with one button?
    Thanks,
    Bob

    Hi,
    commit doesn't execute before a field is submitted. So what you do is you submit a page then update the field (which then is not yet reflected in the submit) an call commit, which basically executes on no new data. In the second call you now submit the data shown in the field that then also gets commited. To get it commited on the first button press, set the field value to the binding layer (attribute binding or iterator binding )
    Frank

  • Af:statusIndicator does not show busy icon when a command button is click

    Hi Guys,
    af:statusIndicator does not show busy icon or motion when a command button is click
    I am working on an excel data upload functionality on .jspx page. I use “af:inputFile” file uploader to upload an excel file then process the data and store it as a list of objects in memory and display it in “af:table” table
    I added “af:statusIndicator” to the page to show the user that the page is progressing while the data is uploading and when it is saving the data to the database.
    In this case, when the “af:inputFile” is clicked to upload the excel file - the status indicator shows a progress icon (movement) which is expected and is good. However, after the data have been display in the table when I click on a command button that saves the data to the database – I expected the status indicator to start its busy motion but that is not happening. Whereas, the command button grayed out and is disable when I clicked the button until the operation is completed.
    Is there any way to start the statusIndicator when a command button is clicked?
    I tried the following options
    *<af:statusIndicator id="si1_uploadStatus" partialTriggers="pc1:cb1 pc1:table"/>*
    Where pc1:cb1 is the command button and pc1:table is the table
    *<af:commandButton text="Submit Uploads" id="cb1"*
    *disabled="#{!viewScope.batchUploadController.allSavable}"*
    *partialTriggers="::infFilePath"*
    *action="#{viewScope.batchUploadController.saveUploadedData}"*
    *blocking="true"/>*
    Thanks,

    Can somebody please address this?
    Thanks,

  • Command buttons best practice

    Hello,
    I would like to ask how others design their GUI with several command buttons (OK button Boolean).
    For instance, there is a simple application where the user can start data acquisition by clicking on a button with text "Start monitoring". Instead of having another button with text "Stop monitoring", usually I just change the button label text into "Stop monitoring", so it is obvious to the user that again clicking on it will stop the monitoring process of the app (in the event case of this button I read out the actual label text with property node in order to decide which action to message to the DAQ loop from the GUI Event handler loop).
    If I have another button with label text like "Start file record", I do the same way: after starting file record, I change the text to "Stop file record".
    To avoid unnecessary extra programming, this button is only in Enabled state if the application is already in the "monitoring" state. Also, if there is an ongoing file record (+ DAQ obviously), the user cannot operate the "Stop monitoring" button. So depending on the state of the applications, some buttons are Enabled, some in "Disabled and grayed out" state.
    I wonder how others are doing their GUI/application?
    I am not sure if this is a good way to do, but at least I can avoid extra state check programming and minimizing the number of buttons...
    Solved!
    Go to Solution.

    Also booleans can have three different images associated with them (well more for things like mouse over but that's not what  I mean).  You can have an image that is shown when the button it True, when the button is False, or an image that is shown when it is either False or True.  So on top of having the text show "Start" or "Stop" I usally replace the True image and the False image with a start and stop icon.  Customize the boolean control, and then right click and choose Import Picture From Clipboard and select the appropriate state.
    Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
    If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

  • Show/Hide Command button in ADF

    I want to hide "Command Button" based on the select of "tableSelectOne". I have tried using the following code but I am not able to do that. So pls suggest some other options.
    <af:panelGroup partialTriggers="DestRulesSelectionId">
    <af:commandButton text="..."
    disabled="false"
    shortDesc="Test"
    partialTriggers="DestRulesSelectionId"/>
    </af:panelGroup>
    <af:tableSelectOne text="Select and" autoSubmit="true"
    id="DestRulesSelectionId"/>

    Hi Didier,
    But I have also developed the same example and it is working, without putting the command button under any parent component.
    Page defination is
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
              xmlns:h="http://java.sun.com/jsf/html"
              xmlns:f="http://java.sun.com/jsf/core"
              xmlns:af="http://xmlns.oracle.com/adf/faces"
              xmlns:afh="http://xmlns.oracle.com/adf/faces/html">
      <jsp:output omit-xml-declaration="true" doctype-root-element="HTML"
                  doctype-system="http://www.w3.org/TR/html4/loose.dtd"
                  doctype-public="-//W3C//DTD HTML 4.01 Transitional//EN"/>
      <jsp:directive.page contentType="text/html;charset=windows-1252"/>
      <f:view>
        <afh:html binding="#{backing_ShowHide.html1}" id="html1">
          <afh:head title="ShowHide" binding="#{backing_ShowHide.head1}" id="head1">
            <meta http-equiv="Content-Type"
                  content="text/html; charset=windows-1252"/>
          </afh:head>
          <afh:body binding="#{backing_ShowHide.body1}" id="body1">
            <h:form binding="#{backing_ShowHide.form1}" id="form1">
              <af:panelPage title="Show Hide" binding="#{backing_ShowHide.panelPage1}"
                            id="panelPage1" partialTriggers="selectOneRadio1">
                <f:facet name="menu1"/>
                <f:facet name="menuGlobal"/>
                <f:facet name="branding"/>
                <f:facet name="brandingApp"/>
                <f:facet name="appCopyright"/>
                <f:facet name="appPrivacy"/>
                <f:facet name="appAbout"/>
                <af:selectOneRadio label="Select "
                                   value="#{backing_ShowHide.radioBtnValue}"
                                   autoSubmit="true"
                                   binding="#{backing_ShowHide.selectOneRadio1}"
                                   id="selectOneRadio1">
                  <af:selectItem label="One" value="one"
                                 binding="#{backing_ShowHide.selectItem1}"
                                 id="selectItem1"/>
                  <af:selectItem label="Two" value="two"
                                 binding="#{backing_ShowHide.selectItem2}"
                                 id="selectItem2"/>
                </af:selectOneRadio>
                <af:commandButton text="commandButton 1"
                                  binding="#{backing_ShowHide.commandButton1}"
                                  id="commandButton1"
                                  partialTriggers="selectOneRadio1"
                                  rendered="#{backing_ShowHide.radioBtnValue =='one'}"/>
              </af:panelPage>
            </h:form>
          </afh:body>
        </afh:html>
      </f:view>
      <!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_ShowHide-->
    </jsp:root> ~Vikram
    http://kohlivikram.blogspot.com/
    Message was edited by:
    KoVik
    Message was edited by:
    KoVik

  • Disable a button component onClick

    hi,
    I am work with JSF technology. I have a requirement based on command Button i.e..
    can we create make a command button disabled on click and the request is to be send to the server
    scenerio:
    In my application if the user clicks multiple times the submit button. the application is throwing an exception. So I want to disable the submit button when the button is first clicked and the data is to be sent to the server.
    I tryed this using JavaScript . I was able to disable the button on click but the request was not sent
    can Anybody help me in solving this issue. I will be very thank full if i get the help.
    thank you.

    You can also use javascript instead.
    onClick="window.setTimeout('document.getElementById(\'' + this.id + '\').disabled = true, 50);"
    Dependent on the security requirements of your app you can't rely on this client side behaviour. The user could manipulate the request and invoke the action method, even if the button is disabled.

  • Controlling the desableing of command buttons

    I have been having a great deal of trouble trying to work out how to control the command button such that if the rowset is null then the button is disabled. The trick is that the rowset is not defined by the view where the command button is located. The rowset is defined by a view which has a "view" command button which displays the specific row selected, then this view has a command button that will display the detail rowset of the selected master row, but if there are no detail records I want the button to be disabled. How can I do this in ADF JSF? If I use a backing bean to make the determination prior to the page rendering then how does the backing mean method set the parameter necessary to disable the command button? Any advice or tutorial that I can use is most appreciated. My goal with using ADF JSF effort was to demonstrate that a complex app could be generated with minimum coding, I would like to keep to this concept if possible. Thanks,
    Michael

    Wrong forum. You need the ADF or JDeveloper forums.

Maybe you are looking for

  • OBPM Studio 10g R3: Create new process instance via PAPI

    Hi folks, I used JDeveloper to generate Java stubs off the PAPI WSDL. This works great and I'm able to list Processes similar to the bundled JAX-WS example just fine. Now I'd like to take it to the next level and create a process instance. I really a

  • I need an app to search PDF, words not in sequential order. Please help

    Hopefully this means something to someone. I need to search through hundreds of PDF files but need to search for the words in the file name in non sequential order.  Every app that I have looked at so far can search for words in the middle of a file

  • Getting HDMI audio working (ASUS P5E-VM HDMI mATX)

    Hey everyone. So I'm trying to create a HTPC using this ASUS P5E-VM HDMI mATX motherboard with a 3.0 GHz E8400 Core 2 Duo and 4GB RAM. I've installed Arch 64-bit on it and have full 1080p video showing nicely on my HD TV with Gnome set up quite nicel

  • Configuring Captivate with SAP

    We are interested in using Captivate for training of SAP basic functions as well as more complex transactions. We are most interested in finding out whether it is possible to enable Captivate files to be called up in SAP's application help (while the

  • Won't publish /asks for password/ won't log in .mac

    My website was working great. I changed my password through inspector. Then when I tried to publish again it put me in .mac sign in page. In the past, iweb usually would just publish without going to the sign in page. I wnt ahead and reentered passwo