[ 
http://issues.apache.org/struts/browse/STR-2527?page=comments#action_37416 ] 

Niall Pemberton commented on STR-2527:
--------------------------------------

I've updated the JavascriptTag's "staticJavascript" attribute to allow runtime 
expressions (so that its consistent with the "dynamicJavascript" attribute) and 
modified the EL version of TLD for the Javascript tag to keep it in line with 
the standard one:

   http://svn.apache.org/viewvc?view=rev&revision=410116

As far as "taglib" sub-project goes this issue is resolved as the only 
attributes where runtime expressions are not allowed are the id attributes (and 
the indexId attribute on the IterateTag).

So what remains is to sort out tiles and there are quite a few attributes where 
runtime experessions are not allowed:

insert (attribute, beanScope, flush)
definition (scope)
put (name, direct, type, beanScope)
putList (name)
add (value, direct, type, beanScope)
get (flush)
initComponentDefintion (file, className)
useAttribute (className)
importAttribute (scope)

Since the tiles tags are more complicated than the standard ones it needs 
someone more familiar with tiles determine which attributes are appropriate to 
change.

> Attributes with <rtexprvalue>false</rtexprvalue> in TLD prevent EL evaluation
> -----------------------------------------------------------------------------
>
>          Key: STR-2527
>          URL: http://issues.apache.org/struts/browse/STR-2527
>      Project: Struts Action 1
>         Type: Improvement

>   Components: Tiles
>     Versions: 1.2.7
>  Environment: Operating System: other
> Platform: Other
>     Reporter: Marc Guillemot
>     Priority: Minor
>      Fix For: 1.3.5

>
> In different tld files, different attributes are configured with
> <rtexprvalue>false</rtexprvalue>
> which prevents using EL in a JSP 2.0 Servlet Container.
> This is the case for instance in
> - html: tag "javascript" attribute "dynamicJavascript"
> - tiles: tag "insert" attribute "attribute"
> - bean: tag "struts" attribute "id"
> I can't recognize any logic explaining why some attributes accept runtime
> expressions and other don't. I think that all attributes should accept runtime
> expression to allow EL use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to