Servlet 3.0 – The Journey Begins Now

The Servlet 3.0 specification is doing rounds of the web these days. Although people have loved to use Servlets for various purposes such as implementing business logic in case of small web applications to using it as a controller in MVC architectures, we are yet to see what power will the new specification unleash to the world of web application development.

On a brief note the Servlet 3.0 specification has been approved in the form of JSR 315 is going to be a part of Java EE 6 as mentioned by SUN:

The JCP has approved JSR 315 (ballot) starting the process that will develop Servlet 3.0. Servlet 3.0 is intended to be part of Java EE 6 together with approved JSRs like JSF 2.1 and JAX-RS 1.0 and several more yet to be launched.

The new specification suggests to bring in the feature of asynchronicity to Servlets. We still can leverage the asynchronous nature in a JEE application with the use of Ajax. Experts think that the Ajax model has a problem in its working which can be seen in this JETTY Continuations theory . Having an inherent quality of server side asynchronous nature means that we wont be having the need of Ajax altogether! Somebody should correct me if I am wrong here.

If we presume that the server which will be based on the new specification, is bound to handle queues for loads of asynchronous requests, then in my opinion it will make the server performance a little slower. I am yet seen an implementation of of asynchronous JAX WS service, so it might be possible that I am bit outdated on that aspect.

But to all my JEE lovers, its a good news that finally we would have something more to cheer about. The good news is that majority of the JCP members have nodded their heads in favor of JSR 315. You can see through their polling results. I think I would need to get my certification for J2EE 1.4 upgraded but I have no complaints. 😀

8 thoughts on “Servlet 3.0 – The Journey Begins Now

  1. Yes… very nice. But they should drop the suggested annotations! Well, some of them anyway. Read my review of the new spec on my website for more information about that.

  2. It would be more cool to be able to specify the url-mapping as an annotation on a method. So requests to /foo can goto one method and /bar can go to another. It can reduce a lot of if-else for servlets which have multiple mappings.

  3. Hi please excuse my errors, it is not my first language. I found your post on RSS directory ”
    Servlet 3.0 – The Journey Begins Now | Techtracer” was generally close to what I was researching for, but after carefully reading through your blog post I still was not able find clean answer to my puzzle and this is driving me lunatic. I enjoy your blog and think it is indeed handy but I think you could make it even better if you polish your internal website search to make it easier for visitors to locate information within your website. You can get this done by adding WordPress plugin… I think addon was called advanced search it has many handy features like searching pages, search comments. If you have any questions about installing addon you can reach me at Thank you I hope you have a outstanding day

Leave a Reply

Your email address will not be published. Required fields are marked *