jsr345-experts@ejb-spec.java.net

[jsr345-experts] Re: Review request: EDR books uploaded to java.net project page

From: Jeremy Bauer <jrbauer_at_us.ibm.com>
Date: Tue, 17 Jan 2012 14:22:01 -0600

Hi all,

A comment on the EDR...

Given that lifecycle callbacks of singleton and stateful bean interceptors
can now run within container managed transactions, I think we need to add
a new method-intf type to the possible values of the
container-transaction->method definition in the DD. The current values do
not provide the ability to specifically target transaction attributes to
this style of interceptor via the DD. The name "LifecycleInterceptor"
seems a good fit. Thoughts?

I've seen at least one location in Javadoc that provides the list of
possible meta-inf values, so at least one, maybe more, updates would be
needed there as well.

-Jeremy



From: Marina Vatkina <marina.vatkina_at_oracle.com>
To: jsr345-experts_at_ejb-spec.java.net
Date: 12/16/2011 06:22 PM
Subject: [jsr345-experts] Review request: EDR books uploaded to
java.net project page



Experts,

I uploaded EDR versions of both books of the EJB 3.2 spec. Please review
the changes before the books go to the JCP site for an official
submission. If you don't have any comments, please let me know if you
are ok with the EDR in its current state.

The books have the change bars (the Optional Chapters changes are very
minor) and all the changes are listed in the Revision History sections.

Other than all the cleanups and clarifications (thank you very much to
everybody who helped with this activity), the following had been added
to/changed in the spec (the corresponding parts of the revision history
are prepended with *New:*) :

* Added asynchronous session bean invocations and non-persistent EJB
Timer Service support to EJB 3.2 Lite.
* Removed restriction to obtain the current class loader; changed ‘must
not’ to ‘should exercises caution’ when using the Java I/O package.
* Added support for the lifecycle callback interceptor methods of
stateful session beans to execute in a transaction context determined by
the bean’s transaction management type and any applicable transaction
attribute.

Have a nice reading!

-marina