Currently, I change the JSP through VI, then shutdown Tomcat inside
Eclipse, then do clean-and-rebuild, then restart Tomcat to test.
There must be a smarter/faster way to test JSP changes.
Thanks for comments,
Jimmy
Daniel Pitts - 01 Jun 2007 20:16 GMT
> Currently, I change the JSP through VI, then shutdown Tomcat inside
> Eclipse, then do clean-and-rebuild, then restart Tomcat to test.
> There must be a smarter/faster way to test JSP changes.
>
> Thanks for comments,
> Jimmy
I don't know about Tomcat, but Resin will detect a modified JSP and
recompile just it.
Perhaps your build-system needs a way to simply copy the JSP files
(rather than a clean-and-rebuild approach).
steen - 01 Jun 2007 20:41 GMT
> Currently, I change the JSP through VI, then shutdown Tomcat inside
> Eclipse, then do clean-and-rebuild, then restart Tomcat to test.
> There must be a smarter/faster way to test JSP changes.
>
> Thanks for comments,
> Jimmy
If you're not using eclipse to edit the jsp's, why run the tomcat
through eclipse ?
If you run tomcat as a standalone, it will detect jsp changes and
rebuild the page.
/Steen
Lew - 01 Jun 2007 23:28 GMT
>> Currently, I change the JSP through VI, then shutdown Tomcat inside
>> Eclipse, then do clean-and-rebuild, then restart Tomcat to test.
[quoted text clipped - 7 lines]
> If you run tomcat as a standalone, it will detect jsp changes and
> rebuild the page.
Conversely, if you use Eclipse (or NetBeans, or many others) to edit the JSP
as well as to run the Tomcat server, the Tomcat server will notice the change
right away. Actually, since both IDEs work by linking to an external Tomcat
server, this answer reduces to the same information others provided.

Signature
Lew
neumannl@gmail.com - 02 Jun 2007 06:18 GMT
> Currently, I change the JSP through VI, then shutdown Tomcat inside
> Eclipse, then do clean-and-rebuild, then restart Tomcat to test.
> There must be a smarter/faster way to test JSP changes.
>
> Thanks for comments,
> Jimmy
Hi,
An easy way the use Eclipse and Tomcat is by using the Webtools (WTP)
for Eclipse as follows:
- install your Tomcat somewhere on your computer, doesn't have to be
your eclipse workspace. :)
- go to http://www.eclipse.org/webtools and download either WTP 2.0 or
WTP 1.5.x. The download page will show you what the Eclipse
prerequisites are. You need them as well. The main difference between
the two versions is that WTP 2.0 is not yet final but it supports
Tomcat 6 with the new Servlet/JSP spec.
- once installed open Eclipse -> perferences -> server and add your
Tomcat installation
- create a "dynamic web project".
- you can simply add/edit your JSP pages from Eclipse. They go in the
"WebContent" folder ot whatever you've named it.
- to run your project you can simply say Run As -> On server, then
select your tomcat runtime and that's it basically.
- if you change your JSP files Tomcat should be able to pick these
changes up without restarting. (There is no real point in editing
these files with VI if you're using Eclipse anyway)
Lars
Jimmy - 04 Jun 2007 22:46 GMT
Thanks for all the answer.
I've tried to use Eclipse's WTP then start Tomcat (external
installation) within Eclipse but edit JSP inside the WebContent
directory using VI. Is there a flag I need to turn on so it will
recompile changes to the JSP? I haven't been able to find it so far.
Thanks,
Jimmy
Laaz - 05 Jun 2007 04:24 GMT
> Thanks for all the answer.
> I've tried to use Eclipse's WTP then start Tomcat (external
[quoted text clipped - 4 lines]
> Thanks,
> Jimmy
Does it work of you edit your files with Eclipse?
And why do you want to edit your files with VI? :)
Lars