I found a possible problem, in the Ajax cycle the newly introduced delay
functionality is per default set to 300 if no delay is given.
This might be problematic. It breaks the behavior of the existing
functionality and might cause problems in component frameworks which rely
on the existing behavior of being queued.
My proposal would be just to make the delay optional only with none being
the default if no delay is used.
Werner
On Mon, Sep 24, 2012 at 11:47 PM, Edward Burns <edward.burns_at_oracle.com>wrote:
> Hello Experts,
>
> Here is the first draft of the JavaOne 2012 expert group draft spec
> snapshot.
>
>
> http://java.net/projects/javaserverfaces-spec-public/downloads/download/JSF_2_2/spec_snapshots/javax.faces-api-2.2-20120924.212754-61-javadoc.jar
>
> It's in maven.java.net at GAV javax.faces:javax.faces-api:2.2-SNAPSHOT,
> but I wanted it to stick around longer then their SNAPSHOT expiration
> policy so I put it in our download area.
>
> I'll very likely produce one more draft before JavaOne, but please take
> a look when you get a chance.
>
> Ed
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | homepage: | http://ridingthecrest.com/
>