Java transient fields should not be considered transient for persistence [DATACMNS-180]

[spring-projects-issues]

Oliver Drotbohm opened DATACMNS-180 and commented

AbstractPersistentProperty treats plain transient fields as transient an thus those fields will not end up being persisted which is probably not in line with what one wants to achieve by making the field transient.

Although the Java specification says transient expresses a property shall not be serialized we actually have to as they are usually reconstituated in a readObject(…) method we cannot call and thus would not recreate the object in a state it was before persisting

---

Attachments:

• mylyn-context.zip (2.60 kB)

Issue Links:

• DATACMNS-1477 Consider Java transient fields as persistence transient
  ("is duplicated by")

Referenced from: commits 031129e, 9c42393

[spring-projects-issues]

Russell Allen commented

I realize this is closed, but... well, here is a case where this change had a negative impact.

I am persisting a sub-class of application event (org.springframework.context.ApplicationEvent). ApplicationEvent extends java.util.EventObject which contains a transient 'source' property (type Object).

Before DATACMNS-180, the event's source was dropped and all was well. With the latest version though, spring-data attempts to persist a complex object from the source property (in my particular case) and fails.

What are my options in this case? The offending property is out of my control (I can't add @Transient to a java.util class.) Is there a way to specify properties to ignore without annotations?

[spring-projects-issues]

Oliver Drotbohm commented

Have you tried overriding the getter and annotating this with @Transient?

[spring-projects-issues]

Russell Allen commented

Ah, that worked!

Thank you