Issues
- adding info level logging into AbstractEntityManagerImpl before calling markAsRollback() methodHHH-10627
- EntityGraph API: subclass subgraph support missing/brokenHHH-10378Resolved issue: HHH-10378Gavin King
- Cannot define Path rooted at a collection join referencing attribute named same as "collection property"HHH-10024Resolved issue: HHH-10024Steve Ebersole
- Bytecode enhancer - consistent handling of persistent attributes (field / property access)HHH-10017Resolved issue: HHH-10017Luis Barreiro
- Gradle plugin does not enhance any classesHHH-10016Resolved issue: HHH-10016Luis Barreiro
- Oracle Dialect override canCreateSchema method to return falseHHH-10015Resolved issue: HHH-10015Andrea Boriero
- SchemaUpdate error if target table name only differs low/up case to existing tableHHH-10011Resolved issue: HHH-10011Andrea Boriero
- Unable to parse cfg.xml file with explicit xsi:schemaLocationHHH-10009Resolved issue: HHH-10009Steve Ebersole
- SessionImplementor.getTimestamp() does not return transaction start timeHHH-10008Resolved issue: HHH-10008Radim Vansa
- Query in context needs precedence over query in cacheHHH-10005Resolved issue: HHH-10005Radim Vansa
- Infinispan 7.x deprecated RpcManager.broadcastRpcCommand(EvictAllCommand,boolean) which is not present in Infinispan 8.0HHH-9999Resolved issue: HHH-9999Paul Ferraro
- @NotNull annotation ignored when persisting or merging entitiesHHH-9982Resolved issue: HHH-9982Hardy Ferentschik
12 of 12
When an exception is being rolled back for the reason of a nested transient object, Hinbernate does not log it. it is better to include a logging in the Class org.hibernate.ejb.AbstractEntityManagerImpl
line 1378 before calling the method markAsRollback(); so that the trouble shooting for such and exception can be found such as
LOG.warn(e.getMessage()); or LOG.inf(e.getMessage());