As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
Looking at the source, the only supported ID types are primitives. There is a comment in the code that goes:
<span class="" style="color: #303336; border: 0px; font-size: 13px;"> Class</span><span class="" style="color: #303336; border: 0px; font-size: 13px;"><?></span><span class="" style="color: #303336; border: 0px; font-size: 13px;"> type </span><span class="" style="color: #303336; border: 0px; font-size: 13px;">=</span><span class="" style="color: #303336; border: 0px; font-size: 13px;"> metaData</span><span class="" style="color: #303336; border: 0px; font-size: 13px;">.</span><span class="" style="color: #303336; border: 0px; font-size: 13px;">getIdType</span><span class="" style="color: #303336; border: 0px; font-size: 13px;">();</span><span class="" style="color: #303336; border: 0px; font-size: 13px;"> <br> </span><span class="" style="color: #858c93; border: 0px; font-size: 13px;">// According to JPA-spec all primitive types (and wrappers) are supported, String, util.Date, sql.Date,</span><span class="" style="color: #303336; border: 0px; font-size: 13px;"> </span><span class="" style="color: #858c93; border: 0px; font-size: 13px;">BigDecimal and BigInteger</span><span class="" style="color: #303336; border: 0px; font-size: 13px;"> </span><br>
By using a generic, the code is passing through a serializable that is not properly matched. Seems this would be a relatively easy override in the JPAEntityMappings class.