Mark Paluch

Thanks for looking into it. There's no consistent behavior we could rely on when unwrapping `EntityManagerFactory`. Using `null` as interface type is indeed problematic as Hibernate and EclipseLink do not...

That's fixed now. Our CI has published new snapshots, care to test against `3.5.2-SNAPSHOT` respective `4.0.0-SNAPSHOT`, available from https://repos.spring.io/snapshot/? ```xml org.springframework.data spring-data-jpa 4.0.0-SNAPSHOT spring-snapshot https://repo.spring.io/snapshot true ```

With your model, you have enabled lazy loading. Consequently, if the lazy collection is requested after the transaction, then there's no longer an active session, and you cannot lazy load...

See also https://github.com/spring-projects/spring-framework/issues/28343

There's some logging inside the MongoDB driver through the `org.mongodb.driver.protocol` logger. ``` 2018-01-18 16:51:07|[main]|[NA]|DEBUG|org.mongodb.driver.protocol.insert|Inserting 1 documents into namespace stackoverflow.sample on connection [connectionId{localValue:2, serverValue:39}] to server localhost:27017 2018-01-18 16:51:07|[main]|[NA]|DEBUG|org.mongodb.driver.protocol.insert|Insert completed 2018-01-18...

We are happy to add additional config options on our side once the feature is available in a released version.

Is this still an issue?

Auditing and validation should be orthogonal aspects that ideally should not affect each other. We're using `Order` to avoid falling into the `Ordered.LOWEST_PRECEDENCE` basket. > This change allows a clean...

Isn't using `@NotNull` on a `@LastModifiedBy` like writing a unit test to verify the framework is working correctly? That being said, I'm not sure what type of issue you're trying...

Feel free to submit a pull request @yangchef1