You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by emerson cargnin <ec...@gmail.com> on 2008/10/21 20:09:36 UTC
Slowly x:forEach/x:out tags
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
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: Slowly x:forEach/x:out tags
Posted by emerson cargnin <ec...@gmail.com>.
Hi guys, thanks for the replies.
It's on the interests of everyone to get this one fixed, been jstl a
especification and the taglibs the reference implementation of those.
I could help in testing this if it's needed. I could help reviewing
and if I can, i could help with some development either. Because
otherwise we will stuck in 1.0.6 forever :)
regards
Emerson
2008/10/27 Kris Schneider <kr...@directthought.com>:
> On Mon, Oct 27, 2008 at 4:19 PM, Henri Yandell <fl...@gmail.com> wrote:
>> On Mon, Oct 27, 2008 at 11:48 AM, Kris Schneider <kr...@directthought.com> wrote:
>>> On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
>>> <ec...@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 <ma...@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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: Slowly x:forEach/x:out tags
Posted by Kris Schneider <kr...@directthought.com>.
On Mon, Oct 27, 2008 at 4:19 PM, Henri Yandell <fl...@gmail.com> wrote:
> On Mon, Oct 27, 2008 at 11:48 AM, Kris Schneider <kr...@directthought.com> wrote:
>> On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
>> <ec...@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 <ma...@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
Re: Slowly x:forEach/x:out tags
Posted by Henri Yandell <fl...@gmail.com>.
On Mon, Oct 27, 2008 at 11:48 AM, Kris Schneider <kr...@directthought.com> wrote:
> On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
> <ec...@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.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: Slowly x:forEach/x:out tags
Posted by Kris Schneider <kr...@directthought.com>.
On Mon, Oct 27, 2008 at 12:44 PM, emerson cargnin
<ec...@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...
> regards
> Emerson
>
> 2008/10/22 Kris Schneider <kr...@directthought.com>:
>> 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/taglibs-user@jakarta.apache.org/msg06341.html
>>
>> On Tue, Oct 21, 2008 at 2:09 PM, emerson cargnin
>> <ec...@gmail.com> 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 <ma...@directThought.com>
>> directThought <http://www.directThought.com/>
--
Kris Schneider <ma...@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
Re: Slowly x:forEach/x:out tags
Posted by emerson cargnin <ec...@gmail.com>.
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 <kr...@directthought.com>:
> 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/taglibs-user@jakarta.apache.org/msg06341.html
>
> On Tue, Oct 21, 2008 at 2:09 PM, emerson cargnin
> <ec...@gmail.com> 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 <ma...@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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: Slowly x:forEach/x:out tags
Posted by Kris Schneider <kr...@directthought.com>.
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/taglibs-user@jakarta.apache.org/msg06341.html
On Tue, Oct 21, 2008 at 2:09 PM, emerson cargnin
<ec...@gmail.com> 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 <ma...@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