Using a Record in NoSQL leads to several problems in turn

[jesse-gallagher]

The initial problem is that ConstructorBuilder uses ServiceLoader on init, which won't fly.

Fixing that, though, leads to "List not implemented yet", which can be fixed by adding a ValueReader that can handle Lists.

However, that then leads to:

java.lang.IllegalArgumentException: argument type mismatch
    java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:77)
    java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:499)
    java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:480)
    org.eclipse.jnosql.mapping.reflection.DefaultConstructorBuilder.build(DefaultConstructorBuilder.java:67)
    org.eclipse.jnosql.mapping.semistructured.EntityConverter.convertEntityByConstructor(EntityConverter.java:190)
    org.eclipse.jnosql.mapping.semistructured.EntityConverter.toEntity(EntityConverter.java:141)
    org.eclipse.jnosql.mapping.semistructured.DefaultEntityConverter$Proxy$_$$_WeldClientProxy.toEntity(Unknown Source)
    ...

Admittedly, I'm not sure whether Record support has made it into the release (1.1.1) version of JNoSQL or if it's still in the works, so it may be that this will improve in time outside of this project.

[jesse-gallagher]

There were a few things going on. Beyond the first two fixes enumerated there, JNoSQL's DefaultConstructorBuilder needed to have its addEmptyParameter method changed to account for primitive values. Beyond that, Expressly (the EL implementation) doesn't yet support Records, so I added a resolver and applied it to the XPages and Pages contexts.