time to clean up some code in the EL implementation...
I don't want to propose a better implementation before a 1.0 release, but there are things _can't_ be released to users since in the future they will work differently.
The main point is: I always thought as EL as a replacement for the current _expression_ sintax inherited from beanutils.
So I expect, in the el version, the following:
<display:table name="requestScope.data">
to be replaced with:
<display:table name="${requestScope.data}">
The way _expression_ evaluation works actually, instead, is crazy! The EL _expression_ is used to evaluate the name of the _expression_ then re-evaluated using the old sintax!
So you can do something like
<% pageContext.setAttribute("sourcename","requestScope.data"); %>
<display:table name="${pageScope.sourcename}">
--> this will evaluated to name="requestScope.data"
--> requestScope.data will be evaluated to {object data in the page scope} in the standard tag
Why? Is this useful to anyone? Do you think we should keep this spaghetti mix forever?
I'm going to definitively kill this in the EL version of table tag... This means that the el tag will never work in replacement of the standard tag without at least replacing the sintax of the name attribute (usually a couple of {} will be enough to fix it).
Since al EL version has never been released, neither in beta, this is the right time to do it... I'm sorry for users who downloaded the snapshot waiting for a release with a similar implementation, but since I didn't see any comment on this absurd thing I'm pretty confident most people will not care about it.
fabrizio
