On Thu, 27 Dec 2001, Andrew (Tver) wrote:
>
> I'm absolutley agree with you in the case of "real" deployment. But
> what about development time? I have about 600 classes in my project.
> Using standard ant build make me to recompile all of them, and so on
> according to ant task. Are you using full deployment process after any
> small modifying of a single file (at development/*debugging* time)?
>
Yes, I really do say "ant deploy" every time through the compile/debug
cycle, and it really does copy everything necessary. Ant is smart about
not copying files that haven't changed, so it only takes a couple of
seconds on a fast machine -- no big deal IMHO.
> BTW, is it possible to do something like
>
> .../manager/reload?path=/myApp
>
> with respect to external classes/jars?
>
You can certainly reload the app this way, but there's no way to reload
the classes from the external JARs without restarting Tomcat. This is due
to restrictions in what Java class loaders let you do -- the only way to
"throw away" an old class is to throw away the entire class loader that
loaded it (which would mean throwing away *all* webapps and reloading
them).
If you're actively developing the classes for external JARs themselves,
put them inside your webapp (in /WEB-INF/lib, or just unpacked under
/WEB-INF/classe) during development, and then package them up when you are
done. That way, you can use the manager's restart capability to pick up
the changes.
> Thanks,
> Andrew mailto:[EMAIL PROTECTED]
>
Craig
--
To unsubscribe: <mailto:[EMAIL PROTECTED]>
For additional commands: <mailto:[EMAIL PROTECTED]>
Troubles with the list: <mailto:[EMAIL PROTECTED]>
