Should @Transient imply @JsonIgnore ?

[StephenOTT]

working with scenarios where a class could have different forms of serialization (java vs smile, etc)

If the kotlin annotation @Transient is applied, should it trigger jackson to apply @JsonIgnore?

The javadoc for @Transient is:

Marks the JVM backing field of the annotated property as transient, meaning that it is not part of the default serialized form of the object.

Just a thought for discussion

[cowtowncoder]

This is a good question. Even keyword transient is tricky, see MapperFeature.PROPAGATE_TRANSIENT_MARKER -- originally thought to only remove field as accessors, but later on requested to be more like @JsonIgnore to also remove the whole property (in case there is a getter).

[k163377]

Fields with the Transient annotation will be transient on Java.
Thus, this seems like an issue to consider with databind.

// original
@Transient
var temp: Any? = null

// decompiled
@Nullable
private transient Object temp;

@cowtowncoder
Can you please forward it to databind or I will close it if there is a duplicate?

[cowtowncoder]

I think that

 MapperFeature.PROPAGATE_TRANSIENT_MARKER

added via FasterXML/jackson-databind#296 in Jackson 2.6 might actually already do what is being asked.

If not, I think that the original submitter (@StephenOTT ) could choose to re-file at jackson-databind (referencing this issue), if further functionality wrt transient is desired.
I am not 100% sure what else might be needed beyond MapperFeature mentioned above.

For now, I think this can be simply closed.

[k163377]

Thanks.

@StephenOTT
If you see a need for a new feature that is not covered by PROPAGATE_TRANSIENT_MARKER, please submit a new issue.