Re: Slowly x:forEach/x:out tags

On Mon, Oct 27, 2008 at 11:48 AM, Kris Schneider <[email protected]> wrote:
> On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
> <[email protected]> wrote:
>> So there is no plans to fix this is future versions?
>
> I'd have to say, no, there doesn't seem to be a plan to fix this in
> Standard 1.1.
>
>> We have quite a few number of x:forEach/x:out on our JSPs. I believe
>> our managers wouldn't be willing to refactor all the pages to switch
>> that for xslt, which I'd believe would be overkill.
>
> Understood.
>
>> Is there someone in charge of the x taglibs?
>
> I suppose that would be Jakarta committers with an interest in the
> Standard taglib. I happen to be one of those, but I'm not actively
> working on it at the moment. It seems like this is really one of the
> worst areas of the implementation, but it's hard to gauge how much
> pain it's actually causing (besides yours, of course). There's not
> much traffic on the Jakarta taglibs lists and I have no idea if this
> ever comes up on other lists/forums. Personally, I'd love to be able
> to fix it, but I just can't promise to be able to make the time to do
> it. Maybe...

It's the ugliest bug in the taglibs. I spent some time on it last
year, but couldn't identify a solution as I was knee deep in copied
Xerces (or was it Xalan?) internals.

Hen