Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I am building a Java servlet which requires some jars(libs) for testing in the local server (e.g. Tomcat), but does not need these when the servlet is deployed to the production server (as these are already available in the production). Are there any best practices / approaches recommended to achieve this?
I would add the library JARs to the local app-server installation, to make it look similiar to the production server you are later deploying to.
In the case of pre tomcat 6:
edit:
In the case of tomcat 6 and later:
The consequence would be that possible other apps you run at your local server will also see this lib. But maybe that is not a problem
Does Tomcat load the same library file into memory twice if they are in two web apps?