I will eventually attach my example (which does work for changing indices), but have found that the screen 3 has some permission issues:-
decodeAIEvents is not defined

Line 3

try

catch(e){}var trString=t+'/'+b.substr(1);var escapeTrString=escape(trString);return escapeTrString}else if(b){try

catch(e){}if(/,ua/.test(b)&&d["ua"]==1&&d["tc"])b+=',acua';l=adx_tri.length

Permission denied for <http://ad.doubleclick.net> to call method Location.toString on <http://localhost:8080>.

Line 0

As I said, this is particular to the iframe in screen3 (some ad permission thing in javascript). Might want to switch out the screen 3 to some other link (icefaces.org??). and see if that helps anything.

workaround is to use a currentTab on the server side that is updated whenever anything is submitted to change the index (so mirror the index with a current TabPane object). Since services expects all attributes to use value binding, it looks like the selectedIndex is updated in updateProperties() in javascript, but the pane is not matched to it (similar to mark's work in use of dynamic updates not resolving certain attributes that are set in the initialize fn of our ace components.
Will create separate example for value binding only, and TODO= modify tabSet component similar to Mark's newer version of slider so dynamic change of index will show correct pane.

In order to ensure value binding works when pushing tabIndex value, then the check for isClientSide should not be done in renderTabBody method of TabSetRenderer. Otherwise, the markup will always reflect the last server side selected Pane which was submitted by the actual component. Yui takes the markup and recreates a new tabview, so not sure this is the most efficient way to do this. However, the markup should always reflect the last submission, so no matter whether server or client-side, the tabIndex should be updated to whatever the last value-bound variable suggests.

Brad....can you please test checkin revision 23960 for this to see if it resolves your particular application?

do we need to do additional error checking to ensure that the index that is submitted (pushed from another component via value-binding) is valid first?

Built the icefaces-ace.jar from the trunk and tested, working in my application.