initShim breaks Spring Data JDBC

Spring folks ignore the transient keyword by design. As a result Spring tries to persist the field and fails.

I tried (without success) adding @Transient to it like this

@InjectTransient
@Nullable
protected abstract Object initShim();


@InjectAnnotation(type = Transient.class, target = FIELD)
@Target(METHOD)
@interface InjectTransient {}

Would be nice to have a solution/workaround

[aurambaj]

I have a similar issue while working with Spring jdbc. Got a working solution relying on unsafeDefaultAndDerived = true. @elucash Is that going to be an issue moving forward since it is the older way of doing things?

(no luck with SYNTHETIC_FIELDS but I may have missed something)

@Immutable
@Value.Style(
    unsafeDefaultAndDerived = true,
    builtinContainerAttributes = false,
    typeImmutable = "*",
    of="new"
)
@InjectPersistenceConstructor
public abstract class AbstractOrganization implements Persistable<UUID> {

  @Value.Parameter
  @Id
  @Default
  public UUID getId() {
    return UUID.randomUUID();
  }

  @Value.Parameter
  @Default
  public Instant getCreatedAt() {
    return Instant.now();
  }

  @Value.Parameter
  public abstract String getName();

  /** for spring jdbc to control new instances if using manually set ids */
  @InjectTransient
  @Default
  @Override
  public boolean isNew() {
    return true;
  }
}

[elucash]

by disabling builtin container handling, Immutables doesnt not consider array as an array but as regular reference type (as anything extending Object) and calls Object.equals. You’ve probably disabled containers to fight something in a way containers work by default, so some other solution may be needed, dunno if this can be solved by jdkOnly or beanFriendlyModifiables. In general, if not for the peculiarities of serialization mechanisms, I would wrap any raw array into either collection or specialized type (ByteString / MyBlob / Data) just for the purpose of controlling toString, equivalence and [de-]serialization (how hard it can be to override some serializers/adapters? well for some technologies this definitely a PITA)