Just popping in for a few comments. If anyone saw the servlet 3.0 presentation, you'd know Jan, Rajiv, and Greg did a great job. I did notice a point of disagreement with greg. He mentioned that the simplest case of async servlets is startAsync followed by a dispatch to generate the response. I would argue that startAsync/complete is the simplest case. This requires no re-dispatch and a re-dispatch should not be needed unless you need something like jsp to do more complex content generation.
Also, it was not mentioned that the web fragment ordering effects and restricts annotation scanning as far as I recall. This is important to be able to prevent "rogue" framework jars from putting out servlets that can service requests without your knowledge
12 years ago
1 comment:
Java Servlet 3.0 is a major revision of the Java Servlet specification and includes changes to enable pluggability of frameworks, ease of development, support for async processing, security enhancements, and other minor updates to the existing APIs. This session gives you an overview of the new features with focus on extensibility and async features. In addition to discussing the new features, the session includes demos that show the implementation of the specification in action with the GlassFish application server implementation.
32GB SD Karte
Post a Comment