Let's start rolling...
To recap, at the bottom of this email is the list of proposed features
for the JSR-345 from the EJB 3.2 proposal on the JCP page.
I'd like us to follow these rules:
- If you would like to discuss an item from the list or are proposing a
new feature (or clarification to the existing spec), *please* start a
new thread with the subject to reflect that.
- If you want to log something as a possible item to look at later, feel
free to open an RFE in the issue tracker
(
http://java.net/jira/browse/EJB_SPEC). But let's not use the issue
tracker as the discussion vehicle.
- If you are proposing any item of the EJB technology for the
re-factorization, please keep in mind that any such re-factorization
will require changing the package name, i.e. it will result in the same
API/annotation available the "new" way and the "old" way for backward
compatibility. We cannot just take out a piece of the spec and move it
somewhere else. It will also mean an agreement with the JavaEE EG on the
solution (and probably the Platform spec or a separate document under
the Platform spec, as the location).
----------------
The goal of Enterprise JavaBeans 3.2 is to [...] continue to simplify
the EJB architecture as well as to provide support for the Java EE
platform-wide goal of further enabling cloud computing. The scope of EJB
3.2 is intended to be relatively constrained in focusing on these goals.
Aspects that are planned to be considered in this work include, but are
not necessarily limited to, the following:
* Further enablement for use in the cloud. EJB 3.2 will consider
enhancements to the EJB architecture to enable the Platform as a Service
(PaaS) model for applications using the EJB architecture in accordance
with the directions of the Java EE 7 Platform JSR. This will include an
investigation for the support of multiple tenants.
* Investigation of the potential factorization of the EJB technology
to enable use of container services that it currently provides by other
component technologies of the Java EE platform. The separate
"Interceptors" document is an example of such factorization as was
achieved by EJB 3.1. It is expected that the EJB 3.2 Expert Group will
investigate the area of container-managed transactions as the first
target area for further factorization.
* Alignment and integration with the simplifications and
enhancements made by related JSRs within the Java EE 7 Platform umbrella
(e.g., CDI, JMS, Bean Validation, ...)
* Further use of annotations to simplify the EJB programming model.
* Specifying as optional earlier EJB technology designated as
"proposed optional" in the Java EE 6 Platform specification: namely, EJB
1.x and 2.x entity beans and the required support for web service
invocations via JAX-RPC. An implementation is permitted but not required
to support such optional features.
----------------
Best regards,
-marina