Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: more about custam tag life cycle
Date: Mon, 3 Feb 2003 14:53:31 -0500
Message-ID: 
 <66337F04F2A1E440BF87F2080B5F537001481DF3@madison.dc.Blackboard.com>
Thread-Topic: more about custam tag life cycle
Thread-Index: AcLLvPcsBL0Z8ideS42al38NT7siagAAL6rg
From: "Tim Moore" <tmoore@blackboard.com>
To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>

> -----Original Message-----
> From: Felipe Schnack [mailto:felipes@ritterdosreis.br]=20
> Sent: Monday, February 03, 2003 2:46 PM
> To: Tomcat Users List
> Subject: RE: more about custam tag life cycle
>=20
>=20
> > >   I'm curious, how you get a PageContext when the container
> > > doesn't call setPageContext? Which container have this behavior?
> > What he meant is that it may not call setPageContext *on each=20
> > invocation*.  It will always be called at least once before=20
> > doStartTag.
>   But each invocation shouldn't get a different pagecontext?=20
> PageContext isn't=20
> something related to request's URL? I guess pagecontext's=20
> functionality isn't very clear to me...

We're talking about reuse within a single page.

> > >   I don't see a reason why we should have pool-specific
> > > method for tag property cleaning. doFinally method is=20
> > > intended for tag cleaning... Probably when created it was=20
> > > intended for cleaning resources like database connections,=20
> > > etc but I don't see any reason to create yet another method=20
> > > just for tag reuse
> > I think there might be some benefit in clarity to the tag=20
> developer.=20
> > The current lifecycle behavior seems to confuse a lot of=20
> people (and I=20
> > was certainly one of those people when I first started writing tag=20
> > extensions).
>   Yes, but add even more method would make it easier? Maybe=20
> just the way=20
> the current methods are "defined" in the docs should be=20
> changed. If you make it clear that doFinally() is ok for tag=20
> reuse cleaning, everybody will use it for this.

Except that it's not, really.

> > But when I made a suggestion like that on the tomcat-dev=20
> list, it was=20
> > pointed out that JSP 2.0 offers a new SimpleTag interface that will=20
> > never be pooled, and is much more straightforward than the "classic=20
> > tag" interface.  Hopefully in the future most tags can use that=20
> > interface instead, and the classic Tag interface can be=20
> reserved for=20
> > the rare tags that benefit from reuse.
>   Tag reusing is so rare to be useful at all? Why?

Well I guess that's the conclusion they came to by JSP 2.0, and the
rationale behind the SimpleTag interface.

--=20
Tim Moore / Blackboard Inc. / Software Engineer
1899 L Street, NW / 5th Floor / Washington, DC 20036
Phone 202-463-4860 ext. 258 / Fax 202-463-4863


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