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.
We usually get a servlet-api.jar along with web/app server.
Like as the remnant of the whole Java EE API, the Servlet API is abstract.
SunOracle doesn’t provide any code. The contract is definied on paper (API specification, javadocs, etc). The implementors have to provide the concrete API and implementation themselves which comply the specs/javadocs. But there’s usually a so called “reference implementation” whose code may be shared/reused/forked for other implementations. Until with Servlet 2.5, this used to be Apache Tomcat. For Servlet 3.0 this is Glassfish.