: nyhgan [mailto:[EMAIL PROTECTED]
>Sent: Wednesday, May 19, 2004 3:35 PM
>To: Tomcat Users List
>Subject: RE: Conceptual Doubt
>
>
>
>
>For yet other actions, such as modifying a class under WEB-INF/classes,
you
>don't even
>need to restart the webapp: set reloadable=
For yet other actions, such as modifying a class under WEB-INF/classes, you don't even
need to restart the webapp: set reloadable="true" for your context and
development="true" for the JSP servlet (which is the default).
>> One question. What exactly happens when it reloads a class? If the cl
>
> You need to restart tomcat when you change server.xml. For other
> actions, such as adding a new webapp, or modifying a webapp's web.xml
> file, you need to restart the webapp: that can be done using Tomcat's
> Manager webapp without restarting the server itself. For yet other
> actions, suc
Hi,
> I want to know as to how and when do we need to restart the
tomcat
>server, It is Everytime I add a new JSP/ a new Bean/new Project etc
Also
You need to restart tomcat when you change server.xml. For other
actions, such as adding a new webapp, or modifying a webapp's web.xml
file, y
Hi all,
I am new to list, joined this for asking some basic questions, I
have in my mind after I having I started using Eclispe/Tomcat/sysdeo and
Lomboss.
I want to know as to how and when do we need to restart the tomcat
server, It is Everytime I add a new JSP/ a new Bean/new Pr
