Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Had the same problem, or at least which looked the same. (You can move directly to my solution in the last paragraph.) Lots of debugging have shown the following:</p> <p>if accessors on that line (mentioned in your question) are null, then <code>accessors = PropertyInfoSetResolver.resolveAccessors(source, type, configuration)</code> line in TypeInfoImpl class is executed, and the reason of exception in my case was this call:</p> <p><code>valueReader.get(source, memberName)</code> at the following piece of code at 'resolveAccessors' method in the PropertyInfoSetResolver class:</p> <pre><code>if (valueReader == null) resolveProperties(type, true, configuration, accessors); else { NameTransformer nameTransformer = configuration.getSourceNameTransformer(); for (String memberName : valueReader.memberNames(source)) accessors.put(nameTransformer.transform(memberName, NameableType.GENERIC), new ValueReaderPropertyInfo(valueReader, valueReader.get(source, memberName), memberName)); </code></pre> <p>which ends up in <code>source.getValue(memberName.toUpperCase())</code>, where <code>source</code> is JOOQ's Record; InvoiceRecord in my case. And - tada - for some reason <code>invoice.getValue("INVOICE_ID")</code> ends up in the exception (no such field and therefore <code>indexOf</code> returns <code>-1</code> which causes the ArrayIndexOutOfBoundsException), while <code>invoice.getValue("invoice_id")</code> is totally fine.</p> <p>So <code>else</code> condition (the same piece of code above) wasn't the right way to execute the code, and <code>if</code> case turned out to be ok.</p> <p>So that's what helped me in my particular case: removing of the row <code>modelMapper.getConfiguration().addValueReader(new RecordValueReader())</code>. Hope this will help you too.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload