Originally posted by Nitin Shivaram:
I wouldn't know which is the absolute correct way to do things, but what i do want to tell you is how i work at my office.
We at our office have two servers, one for development and testing and the other for production.
The m/c which is used for development and testing has two servers running on it, one being used for development and the other for testing.
I personally wouldn't recommend working on the local m/c because if you are working on a large application, then you need to recreate everything that is there on the server on your local m/c which is not good at all, agreed hard disk space is not a problem, but there would be dependencies such as packages, class files and other resources such as html files, images etc, you wouldn't want to waste your time copying all these resources to the local system from the server and vice-versa.
And when i say work on the server, i mean telnet'ing to the server, not physically sitting on the server !!
And btw, did you check whether it was a problem with caching(this is regarding the class file).
Hope this helps
Seriously Rick? Seriously? You might as well just read this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton