On Thu, 3 May 2001, Endre St�lsvik wrote:
> On Wed, 2 May 2001, Joel Parramore wrote:
>
> | Well, Endre, comments such as "classloading is totally fucked",
> | while having a nice kewl sound-bite quality, really don't explain
> | what is going on too well to someone who hasn't encountered the
> | problem before.
>
> It's just that it kind of annoys me. It's definately an huge itch,
> but I don't have the time to scratch it. Stupid thing to say, but
> what's annoying is that it's not quite recongized by the developers
> as a problem, which truly puzzles me..
How do you know they don't consider it a problem? Maybe it's not as
easy to solve as you think it is. Or maybe there are other things
they consider higher priority. Maybe you can contribute some time and
code the solution yourself.
> I have to restart tomcat each and every time I make one single
> change to _anyting_ of my code. This is the most time consuming part
> of developing on Tomcat, I feel. (How's Jetty doing, btw??)
*Every* time, for any change? That doesn't sound right. Servlet
reloading works for me (I'm using Tomcat 3.2.1). The
classloader/class cast issue is different than simple reloading of
servlets.
> Also, forgot to mention, the reloader doesn't notice if any _other_
> classes have changed, e.g. your User object or whatever. Only the
> directly affected Servlet, and only the first one hit, will get
> reloaded.
[ ... ]
I don't believe this is correct either -- for classes that are in the
servlet directories (as opposed to the classpath), I believe reloading
works.
Maybe your app could use some reorganizing.
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
