----- Original Message ----- > From: "Caldarale, Charles R" <chuck.caldar...@unisys.com> > To: Tomcat Users List <users@tomcat.apache.org> > Cc: > Sent: Tuesday, July 24, 2012 6:05 PM > Subject: RE: Project will not build > >> From: Cotton, Joseph B [mailto:bcot...@dpscs.state.md.us] >> Subject: RE: Project will not build > >> Isnt /WEB-INF/lib a Tomcat folder? > > Not really. It's usage is defined in the servlet spec; the Tomcat doc > avoids duplicating information from the spec, since that's required reading > before embarking on a servlet project. > >> Which leads to my other question, if I make a backup of the folders, >> why didn't just copying the the folders back in fix it? There seems >> to be multiple places to configure... > > Again, you're asking NetBeans questions, not Tomcat ones. The IDEs often > have ideas of their own about how to set up and configure a project, to the > point that some of them completely ignore and override the configuration in > the > Tomcat .xml files. > > - Chuck
In my experience, NetBeans is really good about not doing the wrong thing. 1. You define a dependency in your project on the server you've registered with the IDE NetBeans will then add all of the jars found in CATALINA_BASE. This includes not only the standard jars, but things like JDBC drivers that you've added in there. 2. Do NOT make a WEB-INF/lib in your project NetBeans will create that in the war file. If you need to add third party jars in your project, put them somewhere else and add the jars in Project->Properties->Libraries. Better yet, use Ivy or Maven . . . . NetBeans supports both. You can also add libraries / jars solely for testing, as well as adding them solely for compilation (but not packaging in the war file). 3. Netbeans offers lots of standard jars as packages (the standards.jar and taglibs.jar is one) Use those instead of copying your own around. 4. NetBeans uses startup.bat / startup.sh This means it behaves and uses setenv.bat / setenv.bat if found. Basically it's just like running Tomcat from the batch files / shell files. In short, I've found that NetBeans is quite amenable to running stock Tomcat installations. I just untar or unzip a distribution, add the appropriate manager roles and user names (NetBeans will complain if you do not), edit setenv.[bat/sh] to generate JMX, and register it with NetBeans. Log files end up where you expect, with the exception of catalina.out / catalina.[date].out, which is scrolled in two separate output windows. . . . . just my two cents. /mde/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
