users@javaserverfaces-spec-public.java.net

[jsr344-experts mirror] [jsr344-experts] Re: [949-WindowId] Best place to specify creating the windowId?

From: Edward Burns <edward.burns_at_oracle.com>
Date: Wed, 29 Feb 2012 08:29:14 -0800

>>>>> On Wed, 29 Feb 2012 11:38:10 +0100, Werner Punz <werner.punz_at_gmail.com> said:

WP> Hello Ed regarding the actions you required from me
WP> - Update jsf.ajax.response() to cover <update id="javax.faces.WindowId:0" />

WP> a) There I personally think it must also contain the viewroot
WP> like we do it for the viewstate
WP> aka viewroot:divider:windowid, because there can be scenarii with different
WP> window ids per window (subscopes, two different scopes per page thanks to
WP> portlets)
WP> outside of that I am perfectly fine with a new update element.

Ok, great, I'll add the ViewRoot.getContainerClientId() in there.

WP> - Add jsf.getWindowId(form)
WP> I personally think your approach covers only a subset of all possible
WP> usecases, take my code as discussion base. I have covered everything
WP> Leonardo has mentioned and multiple form scenarii)

Certainly, my approach was just a placeholder.

WP> My approach simply is that I deal with an arbitrary root element and
WP> determine the child forms, if no windowId element is found I revert to the
WP> url als last fallback.
WP> If two non matching window elements are found an error is raised.
WP> The frameworks then have to deal themselves with which root element they
WP> take (hence offloading the viewroot handling to the users in that case).
WP> Your form approach is a subset of all this.

Yes, I'll try to understand and integrate your approach.

Ed

-- 
| edward.burns_at_oracle.com | office: +1 407 458 0017
| homepage:               | http://ridingthecrest.com/