tomcat-taglibs-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eduardo Suastegui <>
Subject RE: Problems with Tomcat 4.1.18 and xtags
Date Fri, 14 Feb 2003 15:19:31 GMT
UPDATE: I have disabled pooling, as shown below, and the problem persists:

        <!-- Disable pooling to prevent problems with xtags/XSLT processing

Any other ideas?

-----Original Message-----
From: Eduardo Suastegui []
Sent: Friday, February 14, 2003 7:14 AM
To: 'Tag Libraries Users List'
Subject: RE: Problems with Tomcat 4.1.18 and xtags

Thank you very much for your response. I have browsed through web.xml and
the config documentation, and it isn't terribly obvious how I should disable
tag pooling. Could you point me in the right direction here? Thanks again.

-----Original Message-----
From: Glenn Nielsen []
Sent: Thursday, February 13, 2003 5:55 PM
To: Tag Libraries Users List
Subject: Re: Problems with Tomcat 4.1.18 and xtags

The difference is that Tomcat 4.1 comes with Jasper 2.  Jasper 2 implements
JSP custom tag pooling.  The XTags taglib most likely has some sort
related bug that gets trigger when its tag handlers are pooled.  You can
disable tag pooling in the JspServlet config in your tomcat/conf/web.xml
config file.



Eduardo Suastegui wrote:
> I am running Tomcat 4.1.18 with JDK, and use the xtags directory
> for server-side XSL transformation (XSLT). The first time I access the
> that includes XML to be displayed through xtags' XSLT, it works. The 2nd
> time, it fails (see exception stack trace below), the 3rd time it works,
> 4th time it fails, and so on--odds are okay; evens fail. I do not have
> problem with either Tomcat 4.0.3 or 4.0.6; when I switch to these
> all works as expected. Can anyone throw some help my way? Thanks.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message