-----Original Message----- Date: Mon, 16 Apr 2007 17:18:47 +0200 Subject: Re: component.getClientId only unique to a given page. From: Ed Burns To: de...@ajax.dev.java.net

EB> When using jMaki with JSF, IF there is no "service" attribute but there EB> is a "value" attribute on the a:widget tag, AND the value of the "value" EB> attribute is an EL ValueExpression, THEN there should be no service EB> handed to the widget. Rather, the system should make it so that the EB> postback happens to the regular JSF page. EB> CM> Ed, does this really cover all the use cases? EB> CM> Consider an autocomplete text field ... the fact that I might use a CM> value binding expression on the "value" property is orthogonal to the CM> fact that the widget *also* needs some sort of service callback to get CM> the set of valid options as the user types keystrokes. If I am reading CM> your proposed functionality description right, it would seem to prohibit CM> this kind of combination. EB> EB> Yes. I see. You need the ValueExpression when you render the page, and EB> when the form is actually submitted (via Ajax or otherwise). You need EB> the service only when doing autocomplete *before* the form is EB> submitted. However, as I stated my above rule (which is the same rule EB> for this I've been stating for at least a year) I'm addressing the case EB> where *there is no service attribute* and there is a value attribute. EB> Another clause on the rule is necessary to handle your case. EB> EB> Let me restate my rule to consider your case. EB> EB> if (using jMaki with JSF) { EB> EB> if (no service attribute on tag) {

CM> I am not omfortable with this restriction.

Greg, we need to come to a resolution on this. Please drive it to conclusion. I think all the requirements have been listed elsewhere in this thread.