Do not build JPA types for 'detyped' Hibernate Types (e.g. Envers model) with IGNORE_UNSUPPORTED

Description

As discovered here and here, HIbernate Envers seems to produce ManagedType instances that return null for calls to ….getJavaType() which it must not.

Environment

None

Activity

Show:
Oliver Gierke
July 19, 2016, 4:47 PM

Always the one to prefer a "Look, you're wrong because I say so." over actual arguments. 👏

Steve Ebersole
July 19, 2016, 6:03 PM

If you want to continue rudely arguing on every issues you open in the Hibernate Jira I will disable your account and no longer let you create issues/comment. Seriously, stop being an ass.

Steve Ebersole
July 19, 2016, 6:04 PM

And for what it is worth, I am not the only one on the team that thinks:

  1. You are wrong here

  2. You are rude and argumentative on quite a few issues here

Oliver Gierke
July 19, 2016, 6:15 PM
Edited

If you feel the urge to do so, please go ahead.

If you want to continue rudely arguing …. Seriously, stop being an ass.

Oh, the irony…

Chris Cranford
July 26, 2016, 3:05 AM

For 5.1, I'll leverage the org.hibernate.metamodel.internal.JpaMetaModelPopulationSetting#IGNORE_UNSUPPORTED and ignore MAP mode entities as you suggested. Should users need access to them for any reason, they can always set org.hibernate.metamodel.internal.JpaMetaModelPopulationSetting#ENABLED.

Assignee

Chris Cranford

Reporter

Oliver Gierke

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Major
Configure