Originally posted by P Subramanian:
The same can be achieved if the service method is synchronized. What is the purpose of using the Single Thread model then?
Originally posted by Simon Brown:
At the end of the day, it comes down to personal preference and whether your chosen toolset does the job. If so, there's no point in changing.
However, there are other factors that come into play. For example, our clients tend to look at building high performance, scalable, maintainable component based systems. They have chosen Java/J2EE as their platform on which to do this as it can deliver on all of these requirements. There are many more besides this...
From my perspective, I got into Java over four years ago because it (and its potential) interested me and that's still holding true. It is partly the language, but there's also the other pieces of the puzzle such as the design patterns, the J2EE patterns, architectures for distributed systems and also, the way that "elegant" solutions can be designed and implemented.
This of course all overlaps on to JSPs too. I first saw JSPs at JavaOne (1999 I think) and to be honest, I wasn't impressed at all as it seemed like just another way of building pages to generate dynamic HTML content. However, as the specifications have been enhanced and improved, JSPs are now a very effective tool for building and delivering dynamic content. Couple JSPs with custom tag extensions, JavaBeans, Servlets and the rest of the J2EE and you have a very powerful toolkit.
That's my thoughts ... what does everybody else think?
Originally posted by niranjan pulipati:
Thanks & Regards
Originally posted by Kausik Ghosh:
Best wishes on the launch of your new book :-)
Am currently trying to fathom out the new servlet 2.3 specification which has a lot to do with filtering... questions will follow soon ... ;-)