This looks very interesting -- it would make sense to include a
@WindowScoped annotation if the ID is available.
Does the implementation use HTML5 Session Storage if that's available?
One feature of the ICEfaces WindowScope is immediate cleanup when the
window is closed, but the implementation of this makes use of a
request sent during onunload, and I would say that this strategy
is not solid enough for the JSF standard. However, even if the
scope is not disposed immediately when desired, it would still
be useful in applications (so I'm arguing that we should define
@WindowScoped even if not all aspects of the scope are perfect.)
(Session termination would effectively be relied on for cleanup.)
Cheers,
Ted.
On 2012-01-17, at 2:44 PM, Jakob Korherr wrote:
> Hi experts,
>
> On behalf of Gerhard Petracek, Mark Struberg, Leonardo Uribe, Werner
> Punz and myself, I'd like to send you the window-id proposal, that we
> developed at MyFaces, using MyFaces CODI's window-id handling as basis
> [1]. This proposal contains the basic ideas (classes, methods,
> configuration modes,...) for introducing a window-id in JSF 2.2. You
> can find the related spec issue at [2].
>
> Please review! Further ideas, comments,... are appreciated. Thanks!
>
> Regards,
> Jakob
>
> [1] https://cwiki.apache.org/confluence/display/MYFACES/WindowId+Proposal
> [2] http://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-949
>
> --
> Jakob Korherr
>
> blog: http://www.jakobk.com
> twitter: http://twitter.com/jakobkorherr
> work: http://www.irian.at