...
There's something bizarre going on with this spec and the Expression Language one. The Tomcat release plan indicates there is no JSP 2.2 version. There don't appear to be any JSP 2.2 specifications that can be located, and there are no JSRs at the Sun Java web site related to a JSP 2.2 release. The only references I've managed to find have been a couple of indicators that Glassfish is supporting JSP 2.2, but there don't appear to be any details on what this actually is.
New information has emerged on this spec. There is no JSP 2.2 or EL 2.2 specification. This is, however, a maintenance release of the JSR 245 Specification that contains some minor enhancements to both the JSR 2.1 spec and the EL Information about the proposed changes can be found here.
Component: Expression Language (EL) 2.2
...
The spec version appears to be a bit of a muddle. The spec jar is getting built claiming it is 1.0, but the latest version defined in the Web Profile appears to be in lock-step with the JSP version numbers. It's not clear what version we are actually at currently, but it is possible that there have not been any API changes in this area since the 1.0 version.
It appears that the Web Profile specification has an error in the version number. There is no Expression Language 2.2 specification. However, the JSR 245 Maintenance Release includes some minor updates to the EL specification. These updates are not broken out into a separate spec, but are included under the umbrella of the updated JSP 2.1 spec.
Component: Debugging Support for Other Languages (JSR-45) 1.0
...
Like the web profile itself, this appears to describe a minimal feature set, but an implementation can provide more than the minimum, if desired. This appears fairly easy to meet, once the 3.1 feature set is implemented. Portions of the 3.1 features have already been implemented in OpenEJB.
Additional Notes
The embedded version of OpenEJB is capable of handling a dynamic provisioning of the different subsystems from the Lite profile version up to the full capability (minus the CORBA integration, which is handled by Geronimo). It appears there will be some work required on the part of Geronimo to create profiles/plugins that will selectively start the GBeans that integrate different portions of the OpenEJB stack with the configuration. Currently, the Geronimo EJB configuration is an all-or-nothing proposition.
Component: Java Transaction API (JTA) 1.1
...