[jsr-314-open] So what's left for 2.0?

[Andy Schwartz]

Gang -

Seems like we've still got a few loose ends that we either need to
finish up for 2.0, or, if not, agree to punt on until 2.1.  Based on
recent email threads, these include:

1. State saving

Martin had raised concerns about compatibility between the new tree
visitor-based state saving implementation and the jstl tags.  It sounded
like Martin had a patch - but not sure whether the patch addresses these
problems fully.  Also not sure whether we are providing delta state
saving.  Can anyone clarify what the plan is for 2.0?

2. f:ajax/f:validateBean wrapping behavior

For consistency I think we want to move f:validateBean over to a
wrapping strategy that is closer to f:ajax, but want to hear Dan's take
on this.  (Dan - I can help walk you through the f:ajax implementation
if you have questions about this.)

3. Portlet support

See the "Portlet support - remaining issues" thread for known open issues.

4. Ajax issues

We've got a few minor API-related items that we need to address:

- <f:ajax> should support an "immediate" attribute.
- The AjaxBehavior API still needs some cleanup in order to make it
usable for programmatic cases (eg. need to add typesafe accessors)
- Seems like we never got around to adding support for the @this, @form,
@all, @none keywords in the execute/render lists for
<f:ajax>/jsf.ajax.request(), though think we do want to support these.

4. Behavior issues

The main open issue here is that we need to confirm that Behaviors work
well with composite components, which I believe that Alex has been testing.

Are there any other open issues?  Does anyone have anything to add to
the above comments?

Andy