Tuesday, December 16, 2008

Servlet 3.0 Public Draft

This is in response to Greg Wilkins's blog about the Servlet 3.0 Public Draft.

We have discussed some of the use cases on the EG for things you have said do not have use cases. However, they are not in the Servlet spec and I think they should be. Also, I think your criticism of the JCP should be separate from your arguments about the Servlet spec. They are two different issues and when they are put together it just invites more defensiveness on the part of folks who have a higher interest in making JCP successful. Fixing the JCP is not something that's going to be fixed before we decide on a Final Draft, so I hope we can simply focus on the servlet issues at hand.

I'm not personally a huge fan of using forward semantics in the async case especially because it clears out any content already written which seems like a prime candidate for a reason to keep the wrappers. However, I do think it is better than not having any redispatch ability at all.

I still agree there should be a mechanism for excluding/including jars you need to scan for framework pluggability. However, that is not a showstopper for me and can certainly be a value add feature of any app server.

1 comment:

Sara Reid said...

2009 will be the year of JEE 6. Important specifications in the JEE 6 platform are Servlet and JavaServer Faces. JEE 6 will contain the Servlet 3.0 specification as well as the JSF 2.0 specification. Both are developed in the JCP. JSF 2.0 as JSR-314 (see: jcp.org/en/jsr/detail) led by Ed Burns (Sun) and Roger Kitain (Sun) with participation from almost every vendor in the Java Web Application space. Servlet 3.0 is JSR-315 headed by Rajiv Mordani (Sun); more detail on the JCP Site for Servlet 3.0.

16gb micro sd karte