tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anil K. Vijendran" <>
Subject Re: reloading a jsp bean
Date Wed, 20 Oct 1999 04:35:49 GMT
This is a tricky problem that I haven't investigated well enough.

The problem is if the bean class is newer, then the only way you can reload
it is by creating a new class loader. The whole code out there should
probably rely on a pluggable class loader factory that gives you a new class
loader when you want to reload something. It doesn't.

Another alternative is to drop the context and create a new one...

I'd love to hear if you have any ideas...

Sankar Kondur wrote:

> Hi,
> i am facing a problem. this is the situation.
> i have a jsp file MyJSPFile.jsp in which i am using a bean
> if i make changes in and recompile it and
> then run MyJSPFile.jsp, the changes i made in the bean don't take
> effect. i have to restart tomcat.
> this(making changes to the bean) happens quite frequently in our team.
> i went thru the source code but could not come up with a sensible/simple
> way of getting it done.
> i want to know
> if anybody has faced this problem/requirement?
> does anybody know of a simple way of getting this done?
> also can somebody tell me if this would work - currently the
> uses the parent class loader to do some of the class
> loading. if i put all the class loading functionality into
>, check if the class in the classpath is more recent then
> the class in the hashtable(class-store) and then realod it, will this
> work.
> any help would be appreciated.
> thanks,
> Shankar.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Peace, Anil +<:-)

View raw message