Description Sabine Heider 2009-08-05 09:03:38 EDT

I miss an opportunity to set all array types to mutable on the scope of a persistence unit. While there is a persistence unit property for the temporal types for that purpose (eclipselink.temporal.mutable), it seems that for arrays each field or property would have to be marked explicitly as @Mutable to achieve the same behavior.

There is the following use case for this feature:
We have a large number of JPA applications that have been developed using another JPA provider, which tracks changes even within mutable object per default. We are now considering to migrate all applications globally to EclipseLink. Being able to adjust the behavior of EclipseLink to be the same as the old provider's in this area would help to reduce the migration efforts.