Reviews by real users

Just finished a project using open source libraries and have fresh impressions?

Write a review to share your experiences with open source!

On DevRates we focus on reviews by developers using libraries on their daily work.

Technology radar

Launching a start-up or commercial project using open-source libraries? No time to evaluate various technology stacks?

Interested in the latest trends and top-rated open source projects for all layers of your application?

DevRates contains projects reviews of most popular tagged categories and programming languages.

Build your skill profile

Join DevRates and build your public profile from libraries you know and experience positions from projects you've been involved in.

Follow projects and don't miss any news from blogs and twitter on your wall.

Your company is looking for talented developers? Register on DevRates and show your technology stack on your company profile.


Related project


Review details

Created 7 months ago
Review score is 2

Overall review rating


The most well known and most frequently used servlet container. Works pretty well for what it does (a pure servlet container), but few, very few people would use this as-is. As a rule of thumb people add tons of libraries to Tomcat (like JSF, JPA, CDI, etc). At some you'll be better off installing a readily made full stack, like the Tomcat based TomEE.

One thing that I really dislike about Tomcat is that it copies the context.xml from a war when it first encounters a particular war and stores it internally. If you deploy a new war with a new context.xml, Tomcat will continue using the old one. The Tomcat developers are a HUGE fan of this feature, but I just don't see the point. Why would one ever want to keep the first version of context.xml encountered and silently ignore newer versions?

Nevertheless, this is -the- hallmark for Java based servers, and every Java professional should have Tomcat experience under his belt.

Sign in to vote for review score: 2
Scroll to top