From: Kito Mann <kito.mann_at_virtua.com>
Date: Mon, 12 Jan 2015 12:13:28 -0500

Manfred, can you articulate your objection more clearly? We definitely know
the client id before the JavaScript executes, since it executes on the
client :-).

___

Kito D. Mann | @kito99 | Author, JSF in Action
Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com | @jsfcentral
+1 203-998-0403

* Listen to the Enterprise Java Newscast: *http://
<http://blogs.jsfcentral.com/JSFNewscast/>enterprisejavanews.com
<http://ww.enterprisejavanews.com>*
* JSFCentral Interviews Podcast:
http://www.jsfcentral.com/resources/jsfcentralpodcasts/
* Sign up for the JSFCentral Newsletter: http://oi.vresp.com/?fid=ac048d0e17

On Mon, Jan 12, 2015 at 12:00 PM, manfred riem <manfred.riem_at_oracle.com>
wrote:

> Hi all,
>
> I like to close https://java.net/jira/browse/
> JAVASERVERFACES_SPEC_PUBLIC-49 as "Won't fix" as this request suffers
> from the chicken and the egg problem. In this particular case we cannot
> make sure the client id is rendered before the JavaScript executes.
>
> Thoughts?
> Manfred
>
>