Mailing-List: contact taglibs-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tag Libraries Developers List" <taglibs-dev@jakarta.apache.org>
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <b9943af40810271339k18b3393bp77f3131b2143da4d@mail.gmail.com>
Date: Mon, 27 Oct 2008 16:39:23 -0400
From: "Kris Schneider" <kris@directthought.com>
To: "Tag Libraries Developers List" <taglibs-dev@jakarta.apache.org>
Subject: Re: Slowly x:forEach/x:out tags
In-Reply-To: <31cc37360810271319g789442e7t2f5d90f712573107@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <806d3a1f0810211109y7743826el690e43a777fae1bf@mail.gmail.com>
	 <b9943af40810211641l66c6e234pee1f42e119064d7f@mail.gmail.com>
	 <806d3a1f0810270944x2285b276l8bf775096d6b36b9@mail.gmail.com>
	 <b9943af40810271148n6e12b3c1nae0be1dca2261bfc@mail.gmail.com>
	 <31cc37360810271319g789442e7t2f5d90f712573107@mail.gmail.com>

On Mon, Oct 27, 2008 at 4:19 PM, Henri Yandell <flamefew@gmail.com> wrote:
> On Mon, Oct 27, 2008 at 11:48 AM, Kris Schneider <kris@directthought.com> wrote:
>> On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
>> <echofloripa.yell@gmail.com> 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.

Yup, pretty much exactly where I was at with:

https://issues.apache.org/bugzilla/show_bug.cgi?id=27717#c1 (wow, that
was 4.5 years ago!)

Haven't had the time, or nerve ;-), to go back...yet...

I'm pretty sure I dumped it into an email here a while back, but one
of the things I thought would be worth investigating is to use JAXP
1.3 (https://jaxp.dev.java.net/) and integrate with the
javax.xml.xpath API instead of Xerces/Xalan. I'm pretty sure JAXP 1.3
got backported to Java 1.3, but I'm not sure if the same thing
happened with JAXP 1.4.

> Hen

-- 
Kris Schneider <mailto:kris@directThought.com>
directThought  <http://www.directThought.com/>

---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org