CM> Ed Burns wrote:

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.

CM> Ed, does this really cover all the use cases?

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.

Yes. I see. You need the ValueExpression when you render the page, and when the form is actually submitted (via Ajax or otherwise). You need the service only when doing autocomplete *before* the form is submitted. However, as I stated my above rule (which is the same rule for this I've been stating for at least a year) I'm addressing the case where *there is no service attribute* and there is a value attribute. Another clause on the rule is necessary to handle your case.

Let me restate my rule to consider your case.

if (using jMaki with JSF) {

if (no service attribute on tag) {

if (there is a value attribute) {

the value of the widget "service" property must be the fully qualified URL of the JSF page in which the tag is a component in the view. } else {

either value or service is required. a TagLibraryValidator error?

}

} else {

use the value of the service attribute as the value of the "service" property on the widget.

}

}