Re: In Orion, are tag handler instances reused or reinstantiated?
Hi Bart, It seems that the tags are re-used only when called multiple times inside the same page. At least that is my experience with versions up to 1.4.5 Huibert on 3/1/01 2:25 PM, Trevor Squires at [EMAIL PROTECTED] wrote: > > Funny, I never managed to get it to *not* re-use tags (haven't rev'd up to > latest release tho) regardless of the jsp.reuse.tags setting... > > Trevor > > On Thu, 1 Mar 2001, Jonathan James wrote: > >> Actually it's configurable. Just add "-Djsp.reuse.tags=[false|true]" to your >> command line when you launch the server. >> >> Jonathan >> - Original Message - >> From: "Randahl Fink Isaksen" <[EMAIL PROTECTED]> >> To: "Orion-Interest" <[EMAIL PROTECTED]> >> Sent: Thursday, March 01, 2001 2:47 AM >> Subject: RE: In Orion, are tag handler instances reused or reinstantiated? >> >> >>> Experience tells me they are reused in Orion. If I have an optional tag >>> attribute on a tag and the tag is used multiple times on a page I have >> found >>> out that I need to make sure that any contents set in the optional >> attribute >>> must be cleared manually by me, or I will get whatever contents was set by >> a >>> previous invokation of the tag. >>> >>> >>> Yours >>> Randahl >>> >>> -Original Message- >>> From: [EMAIL PROTECTED] >>> [mailto:[EMAIL PROTECTED]]On Behalf Of Blacha, Bart >>> Sent: 28. februar 2001 19:27 >>> To: Orion-Interest >>> Subject: In Orion, are tag handler instances reused or reinstantiated? >>> >>> >>> We are trying to figure out if tag handler objects are re-used, or >>> instantiated-and-destroyed at every request. This is obviously important >>> for performance reasons. >>> >>> There is conflicting information in JSP spec and on JGuru (see references >>> below). So maybe it's an implementation-specific issue. Which brings me >>> to the question: >>> >>> What does Orion do with tag handler instances? Reuse or reinstantiate >> them? >>> >>> >>> >>> >>> JSP spec 1.1, paragraph 5.4.7: >>> >>> At execution time the implementation of a JSP page will use an available >> Tag >>> instance with >>> the appropriate prefix and name that is not being used, initialize it, and >>> then follow the >>> protocol described below. Afterwards, it will release the instance and >> make >>> it available for >>> further use. This approach reduces the number of instances that are needed >>> at a time. >>> >>> >>> http://www.jguru.com/jguru/faq/view.jsp?EID=337618 >>> >>> Question We want to make sure that our JSP development efforts are >>> thread-safe. Is it possible that two threads will access one instance of a >>> JSP custom tag handler concurrently? >>> >>> No it is not possible. There is a defined lifecycle of a custom tag, and >>> during this lifecycle, that instance of the tag will only get called once. >>> Hopefully in newer implementations of JSP engines, the actual tag object >>> will not get reinstantiated each time (as this negatively affects >>> performance), but at least during it's use, it will be thread safe. >>> >>> >>> -- >>> Bart Blacha, Software Developer >>> NetPerceptions Inc. >>> (512) 349-5622 >>> [EMAIL PROTECTED] >>> >>> >>> >>> >>> >> >> > > >
Re: In Orion, are tag handler instances reused or reinstantiated?
Funny, I never managed to get it to *not* re-use tags (haven't rev'd up to latest release tho) regardless of the jsp.reuse.tags setting... Trevor On Thu, 1 Mar 2001, Jonathan James wrote: > Actually it's configurable. Just add "-Djsp.reuse.tags=[false|true]" to your > command line when you launch the server. > > Jonathan > - Original Message - > From: "Randahl Fink Isaksen" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Thursday, March 01, 2001 2:47 AM > Subject: RE: In Orion, are tag handler instances reused or reinstantiated? > > > > Experience tells me they are reused in Orion. If I have an optional tag > > attribute on a tag and the tag is used multiple times on a page I have > found > > out that I need to make sure that any contents set in the optional > attribute > > must be cleared manually by me, or I will get whatever contents was set by > a > > previous invokation of the tag. > > > > > > Yours > > Randahl > > > > -Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of Blacha, Bart > > Sent: 28. februar 2001 19:27 > > To: Orion-Interest > > Subject: In Orion, are tag handler instances reused or reinstantiated? > > > > > > We are trying to figure out if tag handler objects are re-used, or > > instantiated-and-destroyed at every request. This is obviously important > > for performance reasons. > > > > There is conflicting information in JSP spec and on JGuru (see references > > below). So maybe it's an implementation-specific issue. Which brings me > > to the question: > > > > What does Orion do with tag handler instances? Reuse or reinstantiate > them? > > > > > > > > > > JSP spec 1.1, paragraph 5.4.7: > > > > At execution time the implementation of a JSP page will use an available > Tag > > instance with > > the appropriate prefix and name that is not being used, initialize it, and > > then follow the > > protocol described below. Afterwards, it will release the instance and > make > > it available for > > further use. This approach reduces the number of instances that are needed > > at a time. > > > > > > http://www.jguru.com/jguru/faq/view.jsp?EID=337618 > > > > Question We want to make sure that our JSP development efforts are > > thread-safe. Is it possible that two threads will access one instance of a > > JSP custom tag handler concurrently? > > > > No it is not possible. There is a defined lifecycle of a custom tag, and > > during this lifecycle, that instance of the tag will only get called once. > > Hopefully in newer implementations of JSP engines, the actual tag object > > will not get reinstantiated each time (as this negatively affects > > performance), but at least during it's use, it will be thread safe. > > > > > > -- > > Bart Blacha, Software Developer > > NetPerceptions Inc. > > (512) 349-5622 > > [EMAIL PROTECTED] > > > > > > > > > > > >
Re: In Orion, are tag handler instances reused or reinstantiated?
Actually it's configurable. Just add "-Djsp.reuse.tags=[false|true]" to your command line when you launch the server. Jonathan - Original Message - From: "Randahl Fink Isaksen" <[EMAIL PROTECTED]> To: "Orion-Interest" <[EMAIL PROTECTED]> Sent: Thursday, March 01, 2001 2:47 AM Subject: RE: In Orion, are tag handler instances reused or reinstantiated? > Experience tells me they are reused in Orion. If I have an optional tag > attribute on a tag and the tag is used multiple times on a page I have found > out that I need to make sure that any contents set in the optional attribute > must be cleared manually by me, or I will get whatever contents was set by a > previous invokation of the tag. > > > Yours > Randahl > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Blacha, Bart > Sent: 28. februar 2001 19:27 > To: Orion-Interest > Subject: In Orion, are tag handler instances reused or reinstantiated? > > > We are trying to figure out if tag handler objects are re-used, or > instantiated-and-destroyed at every request. This is obviously important > for performance reasons. > > There is conflicting information in JSP spec and on JGuru (see references > below). So maybe it's an implementation-specific issue. Which brings me > to the question: > > What does Orion do with tag handler instances? Reuse or reinstantiate them? > > > > > JSP spec 1.1, paragraph 5.4.7: > > At execution time the implementation of a JSP page will use an available Tag > instance with > the appropriate prefix and name that is not being used, initialize it, and > then follow the > protocol described below. Afterwards, it will release the instance and make > it available for > further use. This approach reduces the number of instances that are needed > at a time. > > > http://www.jguru.com/jguru/faq/view.jsp?EID=337618 > > Question We want to make sure that our JSP development efforts are > thread-safe. Is it possible that two threads will access one instance of a > JSP custom tag handler concurrently? > > No it is not possible. There is a defined lifecycle of a custom tag, and > during this lifecycle, that instance of the tag will only get called once. > Hopefully in newer implementations of JSP engines, the actual tag object > will not get reinstantiated each time (as this negatively affects > performance), but at least during it's use, it will be thread safe. > > > -- > Bart Blacha, Software Developer > NetPerceptions Inc. > (512) 349-5622 > [EMAIL PROTECTED] > > > > >
RE: In Orion, are tag handler instances reused or reinstantiated?
Experience tells me they are reused in Orion. If I have an optional tag attribute on a tag and the tag is used multiple times on a page I have found out that I need to make sure that any contents set in the optional attribute must be cleared manually by me, or I will get whatever contents was set by a previous invokation of the tag. Yours Randahl -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Blacha, Bart Sent: 28. februar 2001 19:27 To: Orion-Interest Subject: In Orion, are tag handler instances reused or reinstantiated? We are trying to figure out if tag handler objects are re-used, or instantiated-and-destroyed at every request. This is obviously important for performance reasons. There is conflicting information in JSP spec and on JGuru (see references below). So maybe it's an implementation-specific issue. Which brings me to the question: What does Orion do with tag handler instances? Reuse or reinstantiate them? JSP spec 1.1, paragraph 5.4.7: At execution time the implementation of a JSP page will use an available Tag instance with the appropriate prefix and name that is not being used, initialize it, and then follow the protocol described below. Afterwards, it will release the instance and make it available for further use. This approach reduces the number of instances that are needed at a time. http://www.jguru.com/jguru/faq/view.jsp?EID=337618 Question We want to make sure that our JSP development efforts are thread-safe. Is it possible that two threads will access one instance of a JSP custom tag handler concurrently? No it is not possible. There is a defined lifecycle of a custom tag, and during this lifecycle, that instance of the tag will only get called once. Hopefully in newer implementations of JSP engines, the actual tag object will not get reinstantiated each time (as this negatively affects performance), but at least during it's use, it will be thread safe. -- Bart Blacha, Software Developer NetPerceptions Inc. (512) 349-5622 [EMAIL PROTECTED]
In Orion, are tag handler instances reused or reinstantiated?
We are trying to figure out if tag handler objects are re-used, or instantiated-and-destroyed at every request. This is obviously important for performance reasons. There is conflicting information in JSP spec and on JGuru (see references below). So maybe it's an implementation-specific issue. Which brings me to the question: What does Orion do with tag handler instances? Reuse or reinstantiate them? JSP spec 1.1, paragraph 5.4.7: At execution time the implementation of a JSP page will use an available Tag instance with the appropriate prefix and name that is not being used, initialize it, and then follow the protocol described below. Afterwards, it will release the instance and make it available for further use. This approach reduces the number of instances that are needed at a time. http://www.jguru.com/jguru/faq/view.jsp?EID=337618 Question We want to make sure that our JSP development efforts are thread-safe. Is it possible that two threads will access one instance of a JSP custom tag handler concurrently? No it is not possible. There is a defined lifecycle of a custom tag, and during this lifecycle, that instance of the tag will only get called once. Hopefully in newer implementations of JSP engines, the actual tag object will not get reinstantiated each time (as this negatively affects performance), but at least during it's use, it will be thread safe. -- Bart Blacha, Software Developer NetPerceptions Inc. (512) 349-5622 [EMAIL PROTECTED]
