In the case of mojarra, the javax.faces.source and javax.faces.partial.execute have the same structure.

Mojarra markup:

<input id="j_idt6:theColours:0" name="j_idt6:theColours" type="radio" value="red">

<input id="j_idt14:theColours2:0" name="j_idt14:theColours2" onclick="mojarra.ab(this,event,'valueChange','@this','@all')" type="radio" value="red">

MyFaces markup:

<input checked="checked" id="j_id76603324_490dfe1:theColours:0" name="j_id76603324_490dfe1:theColours" type="radio" value="red">

<input checked="checked" id="j_id76603324_490dea6:theColours2:0" name="j_id76603324_490dea6:theColours2" onchange="jsf.ajax.request('j_id76603324_490dea6:theColours2',event,

)" type="radio" value="red">

This seems to be a fix in META-INF/internal-resources/javax.faces/jsf-uncompressed-full.js:

/**

• binding contract the javax.faces.source must be set
  */
  //passThrgh[this.P_PARTIAL_SOURCE] = elementId;
  passThrgh[this.P_PARTIAL_SOURCE] = elem.name;

Please take a look at the above myfaces change – we need to decide if they should modify this or if this is still really a problem in our code.

The spec simply says "identifier" rather than ID or name:

http://download.oracle.com/docs/cd/E17802_01/j2ee/javaee/javaserverfaces/2.0/docs/js-api/symbols/jsf.ajax.html#.request

so the test is likely whether the above change fixes the problem. Alternatively, the MyFaces RadioButtonRenderer could be modified to accept a decode from a javax.faces.source that matches any ID it has written.

So it appears that, when using singleSubmit with MyFaces, the "javax.faces.execute" parameter does not include the name of the component. For example, if you run the test case and run the ss.xhtml page:

javax.faces.partial.execute:@this j_id76603324_490dfe1:theColours:0

Running the fajax.xhtml page:

javax.faces.partial.execute:j_id779036716_2e6f2877:theColours

MyFaces looks like it processes things differently with the f:ajax tag whereas with singleSubmit, from the client perspective, it doesn't look like an Ajax request.

Including the element.name is important for things like radio buttons and checkboxes because the id of the radio button/checkbox is indexed:

j_id76603324_490dfe1:theColours:0

but the actual component doesn't include this

j_id76603324_490dfe1:theColours

Without the element.name in this case, MyFaces fails to run the partial execution against the component and it doesn't get decode() 'd.

Mojarra appears to append the element.name to the outgoing request regardless.

               if (options.execute) {
                   none = options.execute.search(/@none/);
                   if (none < 0) {
                       all = options.execute.search(/@all/);
                       if (all < 0) {
                           options.execute = options.execute.replace("@this", element.id);
                           options.execute = options.execute.replace("@form", form.id);
                           var temp = options.execute.split(' ');
                           if (!isInArray(temp, element.name))

                       } else

                       args["javax.faces.partial.execute"] = options.execute;
                   }
               } else

So I've checked in a change to submit.js that appends the element.name to the execute parameter for radio buttons and checkboxes (if it's not already there) which fixes the issue we are seeing. The fix is currently only applied to singleSubmit for radio buttons and checkboxes as that's the only place we are currently seeing this behaviour.