Timeline issues aside, what is the objection to EJB_SPEC-60?
If it is a matter of how useful it is, the EJB EG is very on board and this is our third most popular issue of EJB 3.2.
If it is a matter of size of change, no actual change to the JCA API need be changed. Two spec notes would be nice, but are not strictly required as they are actions taken by the EJB Container. These are:
- A mention that the MDB Container will be offering the inbound connector a MessageEndpoint that is akin to a no-interface view.
- A mention that the MDB Container will inject the bean class into the activation config, should the spec contain a 'beanClass' property.
-David