The Warring States of NPF

The Warring States of NPF (http://www.nuklearforums.com/index.php)

- Dead threads (http://www.nuklearforums.com/forumdisplay.php?f=91)

- - Tomcat (http://www.nuklearforums.com/showthread.php?t=35149)

Anyone know a lot about tomcat?

I don't know why I'm asking here really except these are the forums I currently frequent.

Hrm, No, sorry, I'm mostly a Windows Boy right here. :/ A good portion of our active Userbase is Windows too, although I think Synkronized uses Linux semi-frequently, so S/He might have ventured into toying with Tomcat.

Quote:

Originally Posted by Nikose Tyris (Post 943468)

Tomcat is a java based web server. I got the impression from your post you think its an OS or something. Works in windows too.

Edit: Oh and thanks for the reply. Its nice to get feedback even if its in the negative.

I've pushed out websites with Tomcat before. My experience was in Mac OS X, though it should be mostly the same with a Linux distro.

I was setting up a JSPWiki install, but the general aspects of Tomcat should carry over to various projects.

The problem is this for development I don't like the way eclipse publishes to tomcat using the WTP plugin.

When I developed on Resin we were used to be able to set eclipse's work directory to be a directory served from resin.

This means that altering a JSP didn't require a restart of the server (or application) but also extended to java files.

Now I notice that editing a JSP while tomcat is running does alter the content of that page.

And as JSP's compile to servlets it must be background compiling first to a .java file then a .class file.

How can I achieve this?

Sorry a bit long winded.

I never used Eclipse's plugins for Tomcat. I ran Tomcat separately as its own thing/service. All of my work done in Eclipse is in a working directory, and I either take the server down temporarily to push a newly-compiled version of the source or leave it up and just copy over individual pages.

It sounds like you currently:
- are running Tomcat via Eclipse
- edit pages/JSP in Eclipse and see immediate changes on the server version

but want to:
- edit pages and then push them to the server at your choice

Is that right? Or was it just to not have it compile all the time?

Sortof the other way arround.

I am currently: doing pretty much as described.

I want: to run tomcat outside eclipse. So I can use apache with AJP and have the same effect.

Also eclipse plugin doesn't allow me put the application as root. Which is a pain cause all urls starting with / will change when I put into a production enviornment.

I admit, it has been a while since I set this up. I recall heading to Apache's Tomcat pages and going through their documentation to install it, but I forget how much I had to tweak it for my system (eg: I have scripts in my ~ directory so that, when I open a Terminal, I can start or stop Tomcat as desired).

Since I was working on JSPWiki content, I had a CVS-synch'd JSPWiki project in a workspace in my user directory. Each time I needed to update the JSPWiki webapp on Tomcat, I could build the project (this was managed via ANT) into a .war file that I could deploy in Tomcat, which required a restart if I recall correctly each time (or, if it was just to change a .jsp page and not a .java file, I'd replace the old copy in the Tomcat JSPWiki folder(s) with the new one from my source folders; this did NOT require a restart of Tomcat).

I don't know if any of that is applicable to your situation / along similar lines. I do know that it let me use relative URLs within my webapp and 127.0.0.1:<port>/<app name> as the URL.

yeah the /<app name> I don't like if its going on its own website. That setup would work but means restarting and rebuilding the app the whole time. Which as I'm sure you know is a pain in the ass if your just doing some stylesheet work. I tend to do lots of small changes and like to view between each one.

Regards,
Wesley

Yeah, me, too. I never had to recompile for style changes, though. Regardless, I guess I'd look for a guide/tutorial that can correctly run through the steps you might want to set it up as you want it and get out of Eclipse.