From debugging a Jakarta EE 11 Platform TCK test failure it looks like @Version support might not be in the EclipseLink version included in
glassfish-8.0.0-M11.zip. The tracking issue for the failure is currently platform-tck/issues/2112 [1]. I pushed an EE 11 Platform TCK change to [2] to help with reproducing the test failure.
Does EclipseLink include support for the Version Annotation? It looks like the EclipseLink master branch had recent Version related changes for eclipselink/issues/2343 [3] but I'm not sure if that change is in glassfish-8.0.0-M11.zip yet.
The entity with the @Version is [4]:
"
@Entity
@Table(name = "A_BASIC")
@Access(AccessType.FIELD)
public class ShortClass_Field implements java.io.Serializable {
// ===========================================================
// instance variables
@Id
protected String id;
@Version
protected Short basicShort;
...
"
Note that in EE 10 the Platform TCK test manually set the basicShort property values but in response to TCK challenge 2112 [1], the code is changed to require the Persistence Provider to set the version field. Do we need an EclipseLink tracking issue for adding EclipseLink support for automatically setting the version field?
