JSP versus ASP:-JSP and ASP do have some basic concepts in common. They both make use of simple sever-side scripting to provide access to Web server information and functionality. They both do so using object oriented scripting. And they both started out with similar styles of delimiting this scripting from a page's content. In fact, Microsoft is replacing ASP with ASP+, which is even more like JSP than ASP in that its pages are compiled upon request and run in a 'virtual machine' (which supports multiple languages and is written in C#).
JSP vs ASP.net:-As a self employed web application developer, I've written a few JSP (-Struts) applications. Because Java was a hype when I was studying, JSP was a natural route to follow. I've come to love Java and related techniques. But fearing the risk of being blinded by love, I ask for your opinion wether I should spend my time learning ASP(.net) as well. Until now, I've managed to steer my projects down the Java road, but how fierce should I defend this approach? Are there major benefits of ASP that JSP doesn't have? I've considered the two as equal (although I've always been a Java advocate). Are they? Is it just a matter of taste? Or are there practical issues that can't be remedied by one of them?
Servlets vs JSP:-Servlets and Java Server Pages are complementary APIs, both providing a means for generating dynamic Web content. A servlet is a Java class implementing the javax.servlet.Servlet interface that runs within a Web or application server's servlet engine, servicing client requests forwarded to it through the server. A Java Server Page is a slightly more complicated beast. JSP pages contain a mixture of HTML, Java scripts (not to be confused with JavaScript), JSP elements, and JSP directives. The elements in a Java Server Page will generally be compiled by the JSP engine into a servlet, but the JSP specification only requires that the JSP page execution entity follow the Servlet Protocol.