Re: Basic JSP question
Arne Vajh?j wrote:
Roedy Green wrote:
If you are writing code for JSP, do you have to take the server down
to change the source code? If not, it would seem you would gradually
fill RAM with classloaders and obsolete versions of code. You would
have to shut down periodically to clear that old just out.
Tomcat can be (and is by default) configured to automatically reload
JSP's when changed.
I would recommend to deploy a war file, because that is the EE way.
Where I work, during development, we deploy war files when classes are
changed, but only deploy the JSP's when they are the only things that
change.
The reason for this is our webapps tend to have a heavy start-up time,
and recompiling a JSP takes far less time (by magnitudes)
My understanding from reading on the internet is that class definitions
does get garbage collected when no longer in use.
In theory, yes.
We've had trouble with some apps. I think there is a debate in the EE
world among Hibernate, Sun, and cglib. There is a memory leak when
those three are used together, but switch out any of the components, and
everything seems to work fine.
Like I mentioned in another post, we get around that problem by
disallowing hot-deploys in production.
--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>