Ed Burns wrote:

What do you expect to have happen?

The semantics you earlier proposed (IIUI) said you wanted to render *either* the service attribute (if present) *or* evaluate the value expression and render the value (if there is an expression) *or* do nothing. That does not cover a bunch of important use cases, for example an autocomplete text field, which needs separate mechanisms to render the value (possibly evaluating an expression to do so, but that should be hidden inside the getValue() method of the component, not done explicitly in the renderer) and a method to perform asynchronous callbacks to a business method that offers the current set of values. (And, of course, the value should be included if the widget happens to be inside a <form> that gets posted the old fashioned way.)

We should definitely set up an IRC chat or something where we can talk through semantics on things like this -- if we're trying to establish standard behaviors across toolkits for generic things like "auto complete text fields" and "menus" and "tabbed views", we need to make sure we've covered *all* the relevant use cases ... for JSF wrapped widgets but also for standalone ones yet.

My impression is that a bunch of our semantics are not completely thought through.

Craig