Deferred EL in dynamic attributes

Question

According to the Sun Java EE 5 tutorial, using deferred EL ( #{} syntax) is forbidden for usage in a tag's dynamic attributes.
What's the exact use of making this illegal? (what problem does this rule solve?)
Anyway, I'm asking since I have developed lots of JSF 1.1 components with dynamic attributes that accept EL expressions. Technically it's not a problem. In the tag handler, I just itterate over all collected attributes, check if they're EL using the JSF API and if so create a value binding for them.
However, in JSP 2.1/JSF 1.2 the container prevents the "#{...}" string from reaching my tag handler code. This is very nasty. I can of course disable container evaluation for the entire page, but this is quite an ugly solution.
Is there any neat workaround for this problem?

Answer 1

When in doubt, check
the 2.1 spec. I'm guessing that the tutorial has a
doc error.You're right, I checked the (may 2006) JSP 2.1 spec, and on page 2-72, section 3 it says:
Dynamic attributes must be considered to accept request-time expression values
as well as deferred expressions.So, the tutorial is definitely wrong.
Maybe someone should notify Sun about this? It seems most people would resort to reading tutorials first instead of wading through the spec. Especially if a Sun tutorial states something, many people will probably consider it 'official'. Perhaps even the Tomcat folks have read said tutorial instead of the spec. Using an EL value in a dynamic attribute in Tomcat 6 causes a translation error.
Btw, I'm not 100% sure how to interpret this note from the spec:
Note that passing a String literal as a dynamic attribute will never be considered
as a deferred expression.What other way is there to pass a deferred expression than through a String litteral?