jsr338-experts@jpa-spec.java.net

[jsr338-experts] Re: updated spec draft

From: Linda DeMichiel <linda.demichiel_at_oracle.com>
Date: Mon, 12 Sep 2011 09:47:46 -0700

Hmmm.... I followed the lead of the platform spec in writing this.

Doesn't the "as if" at the top of page 96 and the statement
"Persistence providers may optimize the steps above, e.g. by avoiding calls to the actual CDI SPI and relying on
container-specific interfaces instead, as long as the outcome is the same"
provide sufficient latitude?

The steps listed are intended to nail down the semantics, while still allowing
the possibility of custom implementations of those semantics.

What rewording would you prefer to see?


On 9/12/2011 7:06 AM, Gordon Yorke wrote:
> I am uncomfortable with the spec prescribing the operations the provider must take to acquire an Entity Listener for
> CDI. This is potentially quite limiting on providers and it is unclear what the benefit to end users would be. It should
> be enough to state the events must be called and the listener instance is expected to be non-contextual.
>
> --Gordon
>
> On 9/6/2011 8:12 PM, Linda DeMichiel wrote:
>> I've just uploaded a updated draft of the spec to our project's Downloads area,
>> http://java.net/projects/jpa-spec/downloads.
>>
>> The changes in this draft are fairly constrained, but I wanted to create a
>> checkpointed draft in advance of contemplating any changes in support of
>> unsynchronized persistence contexts.
>>
>> Changes in this draft are the following:
>>
>> Sections 3.5-3.5.2: Support for CDI injection into entity listener classes
>> Section 6.3.1: Addition of method to CriteriaBuilder interface for downcasting of Root objects.
>> Section 7.4: Addition of unwrap method to EntityManagerFactory interface
>> Section 7.10: Addition of unwrap method to Cache interface
>> Section 9.1: Requirement on the Java EE container to pass reference to BeanManager on
>> the createContainerEntityManagerFactory call.
>>
>> The changebars continue to be additive from the last draft, as I am
>> not planning to reset changebars until after we release a milestone
>> draft to the JCP site.
>>
>> Please let me know if you have any comments or corrections.
>>
>> -Linda
>>
>>
>>