[jsr-314-open] [C036-ElInResources] ACTION: Vote: Resource.getInputStream() underspecified

[Alexander Smirnov]

Frankly, both of them seem not as a solution for me ( I prefer to some 
option that distinguish to parse EL or not for individual files - for 
example, by file extension ), so I'll choose DefaultToOptOut option.

On 09/25/2009 08:15 AM, Ed Burns wrote:
>>>>>> On Fri, 25 Sep 2009 08:55:11 +0200, Werner Punz<werner.punz at gmail.com>  said:
>
> WP>  Anyway I think this discussion gets a little bit off topic ;-), wasnt it
> WP>  about how to apply the el to javascripts originally?
>
> Thank you.  Please take the valuable discussion of caching and resources
> to a separate thread.
>
>> From the previous discussion, I draw two alternatives, which I place on
> the table for further debate.
>
> OPTION RestrictAllowableExpressions
>
> With this option, we modify Resource.getInputStream() to state that the
> implementation must evaluate EL Expressions in resource files if and
> only if the expression is simple (not compound) and starts with the
> "resource" implicit object.  Handling of any other kinds of EL
> Expressions requires decorating the ResourceHandler.
>
> OPTION DefaultToOptOut
>
> With this option, we modify Resource.getInputstream() to state that EL
> evaluation in Resource files is disabled by default.  For simplicity, I
> suggest the user convey their intention at a per-application granularity
> using a context-param.  If the user does decide to opt-in, all EL
> Expressions in all resources are evaluated every time the resource is
> served.  Resource.getInputStream() will include non-normative text
> alerting the user to possible scope complications.
>
> I prefer RestrictAllowableExpressions because decorating the
> ResourceHandler is an easy way to allow more powerful behavior.
>
> ACTION: Please voice your opinion by 1700 EDT Monday 28 September 2009.
>
> Ed
>
>