Well actually, I might be able to do some trickeration with naming. Basically, Envers writes the Type#name into the DOM for the attribute type. ATM we just use a descriptive text for the type name so that it renders better. I could instead use a "known-pattern" approach for the name. E.g. rather than "BasicType adapter for AttributeConverter<Name,String>" as the type name, I could use something like "converted::NametoStringConverter". The benefit of that change is that I can then change SimpleValue (where this exception originates) to recognize this pattern and to trigger its AttributeConverter handling logic branch. As an added benefit, this is a (hacky) way to get AttributeConverter support into HBM in general.

Let me play with that