Hi Rainer,
Thanks again! More below....
On 5/25/2011 6:02 AM, Rainer Kwesi Schweigkoffer wrote:
> Hi Linda, all,
>
> there is a file lying around here containing some typos and minor
> issues discovered in the 2.0 spec after final release. I thought this
> might be a good moment to bring them to your attention. References have
> been updated to point to the 5/13711 version.
>
> Best regards
> Rainer
>
>
>
> 3.2.4 p. 80
>
> 2nd sentence : "involves" instead of "involving"
>
fixed
>
>
> 3.2.6 p. 81
>
> 1st sentence : "An entity instance" instead of "A entity instance"
>
fixed
>
>
> 3.7.2 p. 107
>
> What is "update" aiming at for CacheStoreMode USE ?
>
I'm not sure I understand the question. Update updates the cache; use of refresh
should update as well I believe.
>
>
> 3.8.10 p. 130
>
> Last paragraph, 1st sentence : I think the word "locking" should be
> omitted here.
>
fixed
>
>
> 4.3. p.145
>
> 1st bullet : "non-relationship" should be added to both "persistent
> field" and "persistent property", I guess, since 2.2, to my
> understanding, uses the term persistent field/property for both state
> and association fields.
>
I have reworded as "attributes" to cover both.
>
>
> 4.6.4 p. 160
>
> 2nd paragraph : "or as an update item in the update clause of an update
> statement" ought to be added
>
fixed. This would be for use as a new value to an update item in SET clause.
>
>
> 4.6.6 p. 162
>
> I'd drop "other" from the last sentence
>
fixed
>
>
> 4.8 p. 175
>
> 2nd paragraph : To my understanding the first element in the
> enumeration should read "an identification variable that ranges over an
> entity or embeddable abstract schema type".
>
The embeddable case is covered under single-valued path expression. I
have inserted "(range variable)" after "entity" to clarify the identification
variable term.
>
>
> 6.5.9 p. 298
>
> 1st sentence : "An Expression" instead of "A Expression"
>
fixed
>
>
> 6.5.14 p. 305
>
> Second bullet : "as an Expression" rather than "as a Expression"
>
fixed
>
>
> 7.9.1 p. 335
>
> Second bullet on top : "the" instead of "The"
>
fixed
>
>
> 8.2.1.10 p. 349
>
> Example 4 : Why is orm.xml not considered here ? Neither 8.2.1.6 nor
> 8.2.1.6.2 seem to describe this impact of exclude-unlisted-classes.
>
Orm.xml is presumed to not exist.
>
>
> 9.3. p. 361 2nd paragraph 2nd sentence and 9.3.1 p. 361 3rd paragraph
> of javadoc
>
> Either the subject or the predicate requires an ending "s"
>
This is correct use of the subjunctive in English.
>
>
> 9.4.3 p. 366
>
> 1st paragraph : Why is createContainerEntityManagerFactory() not
> mentioned here ? May the conatiner not override provider defaults ? To
> my understanding of 9.5 it may not use the properties of
> PersistenceUnitInfo for that purpose since the javadocs require them to
> reflect the persistence.xml.
>
This area (use of persistence unit properties, etc) is on my list of
cleanup items. I have added to Open Issues.
>
>
>
>
> ---
> Rainer Schweigkoffer SAP AG Walldorf
> Business Solution& Technology TD Core JS&I
> Technology Development Dietmar-Hopp-Allee 16
> Java Server Core D-69190 Walldorf
> JEE Implementation Group phone: +49 6227 7 45305
> Building 3, I.3.14 fax: +49 6227 7 821177
> rainer.schweigkoffer_at_sap.com
>
> Sitz der Gesellschaft/Registered Office: Walldorf, Germany
> Vorstand/SAP Executive Board: Werner Brandt, Angelika Dammann,
> Bill McDermott (Co-CEO), Gerhard Oswald, Vishal Sikka,
> Jim Hagemann Snabe (Co-CEO)
> Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory
> Board: Hasso Plattner
> Registergericht/Commercial Register Mannheim No HRB 350269
>
> Diese E-Mail kann Betriebs- oder Geschaeftsgeheimnisse oder sonstige
> vertrauliche Informationen enthalten. Sollten Sie diese E-Mail
> irrtuemlich erhalten haben, ist Ihnen eine Verwertung des Inhalts,
> eine Vervielfaeltigung oder Weitergabe der E-Mail ausdruecklich
> untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die
> empfangene E-Mail. Vielen Dank.
>
> This e-mail may contain trade secrets or privileged, undisclosed, or
> otherwise confidential information. If you have received this e-mail
> in error, you are hereby notified that any review, copying, or
> distribution of it is strictly prohibited. Please inform us
> immediately and destroy the original transmittal. Thank you for your
> cooperation.
>
>