+!
___
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 Tue, Nov 11, 2014 at 11:22 AM, Edward Burns <edward.burns_at_oracle.com>
wrote:
> Hello Volunteers,
>
> While working on the HTTP/2 Server Push demo for Devoxx I discovered a
> small bug in the spec. Generally speaking, all resource references
> rendered
> by JSF should pass through ExternalContext.encoreResourceUrl().
> Resources references rendered via the Resource ELResolver, such as
> #{resource['myimg.png']}, do not. This is the bug.
>
> I propose we change getValue() in Table 5-13 to require a call to
> ExternalContext.encodeResourceUrl().
>
> Ed
>
>
> --
> | edward.burns_at_oracle.com | office: +1 407 458 0017
> | 0 work days til Devoxx 2014
>