jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Cantrell" <Mike.Cantr...@ind.alcatel.com>
Subject Re: release() methods for jakarta taglibs (fwd)
Date Tue, 22 Oct 2002 18:45:40 GMT
I don't mind doing a patch for mailer.


Henri Yandell wrote:

>Some important questions on the Users list.
>
>dbtags and mailer getting the exact focus, but a more general question
>being asked. Obviously patches would be nice, or even just bug reports.
>
>Any views?
>
>Hen
>
>---------- Forwarded message ----------
>Date: Tue, 22 Oct 2002 12:59:10 -0500
>From: "Halvorson, Loren" <Loren.Halvorson@firepond.com>
>Reply-To: Tag Libraries Users List <taglibs-user@jakarta.apache.org>
>To: 'Tag Libraries Users List' <taglibs-user@jakarta.apache.org>
>Subject: RE: release() methods for jakarta taglibs
>
>This seems very similar to the bug I filed for dbtags last week.
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13667
>Is someone going to go through and clean up these pooling issues?  Or should
>we be submitting patches?
>-----Original Message-----
>From: Mike Cantrell [mailto:Mike.Cantrell@ind.alcatel.com]
>Sent: Tuesday, October 22, 2002 12:31 PM
>To: Tag Libraries Users List
>Subject: release() methods for jakarta taglibs
>
>
>We are encountering some problems with the Jakarta Taglibs with newer
>servlet containers that pool the tag objects (Tomcat  4.1.x and JRun
>4.0). Most of the tags I looked through don't override the release()
>method to reset the initial values and do cleanup.
>
>For instance, the mailer taglib has a tag called mt:addrecipient. If you
>use this tag, each time the page is called the value is just appended to
>the original value. Are there any plans to go through these tags and
>make them "pool safe"?
>
>Example:
>
>    <mt:mail server="smtp">
>        <mt:from><c:out value="${param.mail_from}"
>escapeXml="false"/></mt:from>
>        <mt:subject><c:out value="${param.subject}"
>escapeXml="false"/></mt:subject>
>        <c:forEach var="email" items="${emailList}">
>            <mt:addrecipient type="to"><c:out value="${email}"
>escapeXml="false"/></mt:setrecipient>
>        </c:forEach>
>        <mt:message type="html">
>            <div style="width: 500px;">
>                <c:out value="${param.body}" escapeXml="false"/>
>            </div>
>        </mt:message>
>        <mt:send/>
>    </mt:mail>
>
>Let's assume that emailList contains the addresess: jsmith@foo.com and
>johns@bar.com.
>
>The first time the page is processed, the email sends out emails to:
>
>     jsmith@foo.com, johns@bar.com.
>
>If you hit reload, the email sends out to:
>
>     jsmith@foo.com, johns@bar.com, jsmith@foo.com, johns@bar.com
>
>and if you hit reload again, the email sends out to:
>     jsmith@foo.com, johns@bar.com, jsmith@foo.com,
>johns@bar.com, jsmith@foo.com,
>     johns@bar.com, jsmith@foo.com, johns@bar.com.
>
>
>I've double checked the emailList  and it only contains the original 2
>elements each time the page reloads. It appears that the taglib is
>simply adding  the list to the old list from the Object obtained from
>the pool since there's no release() method to reset the tag's initial data.
>
>
>
>--
>To unsubscribe, e-mail:
><mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail:
><mailto:taglibs-user-help@jakarta.apache.org>
>
>--
>To unsubscribe, e-mail:   <mailto:taglibs-user-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:taglibs-user-help@jakarta.apache.org>
>
>
>
>
>--
>To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>
>
>  
>


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


Mime
View raw message