I created a prototype of moving to javax.el as a potential fix for bug 33934:
https://issues.apache.org/bugzilla/attachment.cgi?id=26179&action=edit
This would allow us to split into three jars:
* standard-impl, with the 1.2 TLDs that would support 1.2 and 1.1 tags
* standard-compat, with
On Oct 7, 2010, at 11:15 PM, Rahul Akolkar wrote:
> On Thu, Oct 7, 2010 at 9:48 PM, Jeremy Boynes wrote:
...
>> A further refinement would be to refactor the 1.0 code to use the JSP EL
>> support from javax.el.
>>
>
>
> 1.0 code? That would preclude its use unless javax.el is provided.
To cla
On Thu, Oct 7, 2010 at 9:48 PM, Jeremy Boynes wrote:
> The 1.0 taglibs included their own implementation of EL. With EL now being
> provided by the JSP container and newer code using the 1.1 tag URIs, this is
> complexity that would not be needed for many newer implementation.
>
> I've been wond
The 1.0 taglibs included their own implementation of EL. With EL now being
provided by the JSP container and newer code using the 1.1 tag URIs, this is
complexity that would not be needed for many newer implementation.
I've been wondering if we could refactor the library into two jars: one
supp
