Re: [jsr-314-open] [C036-ElInResources] ACTION: Vote:Resource.getInputStream() underspecified (was: Evaluating EL in resourcefiles)

I prefer DefaultToOpt"In", but given the choices: +1 for DefaultToOptOut -lincoln Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Ed Burns <Ed.Burns(a)Sun.COM&gt; Date: Fri, 25 Sep 2009 08:15:32 To: <jsr-314-open(a)jcp.org&gt; Subject: [jsr-314-open] [C036-ElInResources] ACTION: Vote: Resource.getInputStream() underspecified (was: Evaluating EL in resource files) 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. 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 -- | ed.burns(a)sun.com | office: 408 884 9519 OR x31640 | homepage: | http://ridingthecrest.com/