custom tags and work dir

[trang le <le...@bellsouth.net>]

1. Although it would be not appropriate to use the term "scope", I found
that custom tags are quite persistent. Once compiled and invoked, they
persist even after I deleted the tag handlers.

2. Perhaps, the only way to stop the effect of tags is to remove the
temporary folder in the work dir. However, last time I did that, all the
customtags stopped working altogether!

So my questions are: (1) what is the life(persitence) of the customtags? (2)
is it advisable to remove the contents of the work dir at all? this last
question apply to tomcat3.1 or later.

TIA

Re: custom tags and work dir

["Craig R. McClanahan" <Cr...@eng.sun.com>]

trang le wrote:

> Hi Craig,
>
> Thank you very mcuh for the response. there is one point I one to clarify.
> Last time when I removed the work dir, tomcat wasn't running. Can I say that
> for customtags, once they are invoked the first time, they are considered
> running even tomcat has been stopped?
>

No ... once you stop Tomcat the custom tags are no longer running.

However, you should note that the custom tag classes themselves are not stored
in the temporary working directory -- they come from your WEB-INF/classes or
WEB-INF/lib directory just like all your bean and servlet classes do.  The
things stored in the temporary working directory are the generated Java source
code (and resulting compiled classes) for your JSP pages themselves.

If you update a JSP source page in your app, Tomcat will notice that next time
you request it, and recompile.  If you modify a custom tag class (or a bean
class, or a servlet class ...) you need to restart in order for the change to
take effect.

>
> I used tomcat 3.1 standalone on win98.
>

Craig


>
> ----- Original Message -----
> From: "Craig R. McClanahan" <Cr...@eng.sun.com>
> To: <to...@jakarta.apache.org>
> Sent: Saturday, August 12, 2000 1:20 PM
> Subject: Re: custom tags and work dir
>
> > trang le wrote:
> >
> > > 1. Although it would be not appropriate to use the term "scope", I found
> > > that custom tags are quite persistent. Once compiled and invoked, they
> > > persist even after I deleted the tag handlers.
> > >
> >
> > >
> > > 2. Perhaps, the only way to stop the effect of tags is to remove the
> > > temporary folder in the work dir. However, last time I did that, all the
> > > customtags stopped working altogether!
> > >
> > > So my questions are: (1) what is the life(persitence) of the customtags?
> (2)
> > > is it advisable to remove the contents of the work dir at all? this last
> > > question apply to tomcat3.1 or later.
> > >
> >
> > Custom tag classes are just like any other Java class -- they are loaded
> the
> > first time they are referenced, and stay there until you reload the web
> > application that uses them.  You can enable reloading on changes by
> setting a
> > property in the $TOMCAT_HOME/conf/server.xml file, although it has been
> reported
> > not to work well in all circumstances.
> >
> > Arbitrarily removing things from the container's temporary working
> directory is
> > like taking pieces off of an automobile engine while you are driving down
> the
> > road -- it's not a very good idea :-).  It is never appropriate to
> arbitrarily
> > modify or remove the contents of the private working files of a server
> while it
> > is running.
> >
> > >
> > > TIA
> >
> > Craig McClanahan
> >
> >
> >

Re: custom tags and work dir

[trang le <le...@bellsouth.net>]

Hi Craig,

Thank you very mcuh for the response. there is one point I one to clarify.
Last time when I removed the work dir, tomcat wasn't running. Can I say that
for customtags, once they are invoked the first time, they are considered
running even tomcat has been stopped?

I used tomcat 3.1 standalone on win98.


----- Original Message -----
From: "Craig R. McClanahan" <Cr...@eng.sun.com>
To: <to...@jakarta.apache.org>
Sent: Saturday, August 12, 2000 1:20 PM
Subject: Re: custom tags and work dir


> trang le wrote:
>
> > 1. Although it would be not appropriate to use the term "scope", I found
> > that custom tags are quite persistent. Once compiled and invoked, they
> > persist even after I deleted the tag handlers.
> >
>
> >
> > 2. Perhaps, the only way to stop the effect of tags is to remove the
> > temporary folder in the work dir. However, last time I did that, all the
> > customtags stopped working altogether!
> >
> > So my questions are: (1) what is the life(persitence) of the customtags?
(2)
> > is it advisable to remove the contents of the work dir at all? this last
> > question apply to tomcat3.1 or later.
> >
>
> Custom tag classes are just like any other Java class -- they are loaded
the
> first time they are referenced, and stay there until you reload the web
> application that uses them.  You can enable reloading on changes by
setting a
> property in the $TOMCAT_HOME/conf/server.xml file, although it has been
reported
> not to work well in all circumstances.
>
> Arbitrarily removing things from the container's temporary working
directory is
> like taking pieces off of an automobile engine while you are driving down
the
> road -- it's not a very good idea :-).  It is never appropriate to
arbitrarily
> modify or remove the contents of the private working files of a server
while it
> is running.
>
> >
> > TIA
>
> Craig McClanahan
>
>
>

Re: custom tags and work dir

["Craig R. McClanahan" <Cr...@eng.sun.com>]

trang le wrote:

> 1. Although it would be not appropriate to use the term "scope", I found
> that custom tags are quite persistent. Once compiled and invoked, they
> persist even after I deleted the tag handlers.
>

>
> 2. Perhaps, the only way to stop the effect of tags is to remove the
> temporary folder in the work dir. However, last time I did that, all the
> customtags stopped working altogether!
>
> So my questions are: (1) what is the life(persitence) of the customtags? (2)
> is it advisable to remove the contents of the work dir at all? this last
> question apply to tomcat3.1 or later.
>

Custom tag classes are just like any other Java class -- they are loaded the
first time they are referenced, and stay there until you reload the web
application that uses them.  You can enable reloading on changes by setting a
property in the $TOMCAT_HOME/conf/server.xml file, although it has been reported
not to work well in all circumstances.

Arbitrarily removing things from the container's temporary working directory is
like taking pieces off of an automobile engine while you are driving down the
road -- it's not a very good idea :-).  It is never appropriate to arbitrarily
modify or remove the contents of the private working files of a server while it
is running.

>
> TIA

Craig McClanahan