On Wed, 18 Jun 2003, Igor Shabalov wrote:
> Date: Wed, 18 Jun 2003 09:16:58 -0700 > From: Igor Shabalov <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Re: Struts Action Scripting > > > Craig, do not tell me that it is impossible, when I've already have this > done in Exadel Application Framework. Yes! Careful work with classloaders > can do the job. This is possible, because Struts runtime control any use of > Action classes, and, presumably, user do not use Action classes directly > from user’s code. > That might work for Actions, but how about for beans in general? Or classes loaded from a parent class loader (like classes from common/lib in Tomcat)? I'm really not interested in trying to support fancy class loading tricks like this, across all platforms, in the Struts codebase itself. It was hard enough to get class loading inside *one* container (I wrote a large chunk of the Catalina code in Tomcat) to work reliably. If you are interested in trying this with Exadel, then more power to you ... and I'll happily send the support questions to your user list instead :-). > Best, > Igor. Craig > > On Tue, 17 Jun 2003 01:02:15 -0700 (PDT), Craig R. McClanahan > <[EMAIL PROTECTED]> wrote: > > > > > > > On Thu, 12 Jun 2003, Igor Shabalov wrote: > > > >> Date: Thu, 12 Jun 2003 11:13:47 -0700 > >> From: Igor Shabalov <[EMAIL PROTECTED]> > >> Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > >> To: Struts Users Mailing List <[EMAIL PROTECTED]> > >> Subject: Re: Struts Action Scripting > >> > >> > >> It's not about compilation time. It's about ability to reload code on- > >> the > >> fly. Here Eclipse do not helps you. Compilation time can be rather > >> small. > >> Time to reload all application will be unacceptable, I just need to > >> reload > >> one action. > > > > Java does not provide any mechanism to unload a previously loaded class. > > The best you can do is throw away the ClassLoader that loaded that class > > (which is what containers like Tomcat do when you reload an existing app) > > . > > > > The fact that JSP pages can be recompiled only works because the > > container > > goes to EXTREME lengths to load the class for each page in a separate > > class loader -- but that doesn't work in the general case, because there > > is no way to know what other classes might refer to a particular class. > > The only safe answer is to reload the app as a whole. > > > > You should give up on the hope of reloading an individual class, and > > instead concentrate on techniques that reduce the reload time of your app > > as a whole. Of course, that's primarily an issue for developers, not > > your > > production deployment, so it is probably not the most important thing to > > spend your time on anyway. > > > > Craig > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > Igor Shabalov > Director of Engineering > Exadel Inc. > http://www.exadel.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
