I�m wondering if any of you guys (and gals) would like to share your thoughts on how to structure the development environment for a Java-based web application. Until now we have only been a few people at a time (1-3) working initially on our lightweight (JSP/Servlet) application. We are using Resin and have so far found Resins built in recompile very satisfactory. We have all our Java source files under the WEB-INF/classes. This means that when Resin looks for changes and recompiles the files, if there is any error, this error will "stop the whole system", since the compile error will show on every page. This is quite OK for now, since we can tell the person in the next room to fix the error. BUT, soon we will be more people developing at the same time, some 500 km apart. Plus some of us are not that very experienced with Java (=possibly frequent errors). We are therefore trying to create a new environment where only the successfully compiled classes are copied to Resins WEB-INF/classes, and the rest is ignored until the error is fixed (solved with some scripts). Is there some commonly used solution to this problem? Does everyone else use versioning systems? We are also encountering some problems that may lead us to using EJBs. How would we set things up then? I read that, for example JBoss has hot redeployment where you can put an updated jar(/war/ear) in the deployment dir. But what if I want to deploy one new class at a time (as we try to do now)? Mattias Jiderhamn Expert Systems [EMAIL PROTECTED] � ==========================================================================To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
