Re: Slowly x:forEach/x:out tags

"emerson cargnin" <[email protected]>
Newsgroups gmane.comp.jakarta.taglibs.devel
Message-ID <[email protected]>
So there is no plans to fix this is future versions?

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.

Is there someone in charge of the x taglibs?

regards
Emerson

2008/10/22 Kris Schneider <[email protected]>:
> I don't believe there's an impending fix for Standard 1.1.x, although
> the bug report (https://issues.apache.org/bugzilla/show_bug.cgi?id=27717)
> does contain some potential approaches. One of the things I mentioned
> in the first comment of the bug report is to try using XSLT as an
> alternative:
>
> http://www.mail-archive.com/[email protected]/msg06341.html
>
> On Tue, Oct 21, 2008 at 2:09 PM, emerson cargnin
> <[email protected]> wrote:
>> I'm using tomcat 5.5.26 and JDK 1.5.
>> After we upgraded standard and jstl version to 1.1.2, the pages
>> started to take more than 30 seconds to render.
>>
>> In this discussion: http://marc.info/?l=taglibs-dev&m=119820558711402&w=2
>> they have the same problem, the context is the same and  they end up
>> finding that the problem is on the implementation of x:forEach and
>> x:out.
>>
>> We reverted to 1.0.6 versions of those jars, but this is a temporary
>> fix, as we want to be able to use features from the new
>> especifications. Reverting fixed the problem.
>> Does anyone know if there is a plan to fix this libraries? Or should I
>> ask this somewhere else? Then please just tell me.
>>
>> regards
>> Emerson
>
> --
> Kris Schneider <mailto:[email protected]>
> directThought  <http://www.directThought.com/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.