PK75616; 7.0.0.1: not insertable, not nullable, and not updatable column issue

Download Description

PK75616 resolves the following problem:

ERROR DESCRIPTION:
A "read-only" column (indicated by insertable=false, updatable=false, nullable=false) is checked for a null value even though it will never be inserted or updated by the JPA provider. The column obtains its value from the database and should not be considered by the JPA provider.

LOCAL FIX:

PROBLEM SUMMARY:

USERS AFFECTED:
All users of Java Persistence API (JPA) with WebSphere Application Server V7.0 entities. A field in the entity must be annotated as nullable=false and either insertable=false and updatable=false

PROBLEM DESCRIPTION:
An exception is thrown when an entity is persisted if it contains a field marked as non-nullable and non-insertable.

RECOMMENDATION:
None

The JPA provider checks for nullable before checking for insertable or updatable.

PROBLEM CONCLUSION:
When a new entity is inserted the check for whether a value may be null is no longer done if the field is not insertable.

When an entity is updated, the check for whether a value may be set to null is no longer done if the field is not updatable.

In short if the field will not be modified the JPA provider does not enforce whether it may be set to null.

The fix for this APAR is currently targeted for inclusion in fixpack 7.0.0.3. Please refer to the Recommended Updates page for delivery information:

http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980