| Re: [nosql-dev] are jakarta.nosql.ValueReader & ValueWriter still relevant? |
You're welcome!I'll provide a migration guide on the Eclipse JNoSQL project.I'm glad that worked.On Tue, Feb 28, 2023 at 8:10 AM Dmitry Repchevsky <redmitry@xxxxxxx> wrote:Great!
You've been already explained that the change was from b5 to b6 (snapshot), but it's great to know that it works!
I am going to stick with b5 and see where jNoSQL is going...
Thank you very much for being responsive.Kind regards,
Dmitry
On 2/28/2023 8:29 AM, Otavio Santana wrote:
Hey Dmitry, it is still working.
I've created this repository as a sample:
On Mon, Feb 27, 2023 at 6:44 PM Otavio Santana <otaviopolianasantana@xxxxxxxxx> wrote:
No problem, Dmistry.
Jakarta NoSQL is the spec, where we discussed focusing only on the mapping as we started the discussion in the e-mail: https://www.eclipse.org/lists/nosql-dev/msg00183.html
This communication belongs not to the spec but to the Eclipse JNoSQL that implements Jakarta NoSQL.
Those are different:
- Jakarta NoSQL: The API
- Eclipse JNoSQL is the framework that implements Jakarta NoSQL.
Please, let me know if there is any question about it.
About the issue, please fire an issue with more details: https://github.com/eclipse/jnosql where we can help you.
On Mon, Feb 27, 2023 at 5:33 PM Dmitry Repchevsky <redmitry@xxxxxxx> wrote:
Hi Otávio,
Now I am even more confused...
After removing Communication API, how I supposed to customize an object serialization/deserialization?Cheers,
Dmitry
On 2/27/2023 5:26 PM, Otavio Santana wrote:
Hey Demistry, how are you?
Those are still valid on version b5.The change happened on version B6:
On Mon, Feb 27, 2023 at 4:03 PM Dmitry Repchevsky via nosql-dev <nosql-dev@xxxxxxxxxxx> wrote:
Hello,
I got an error on my custom jakarta.nosql.ValueReader (aka
https://www.jnosql.org/spec/#_create_custom_writer_and_reader).
> java.lang.UnsupportedOperationException: The type class
> es.bsc.inb.ga4gh.beacon.nosql.MeasurementValueEntity is not supported yet
> at
> org.eclipse.jnosql.communication.ValueReaderDecorator.lambda$read$2(ValueReaderDecorator.java:56)
> at java.base/java.util.Optional.orElseThrow(Optional.java:408)
> at
> org.eclipse.jnosql.communication.ValueReaderDecorator.read(ValueReaderDecorator.java:55)
> org.eclipse.jnosql.communication.DefaultValue.get(DefaultValue.java:46)
> org.eclipse.jnosql.mapping.reflection.AbstractFieldMapping.value(AbstractFieldMapping.java:107)
> org.eclipse.jnosql.mapping.reflection.DefaultFieldMapping.value(DefaultFieldMapping.java:26)
> org.eclipse.jnosql.mapping.document.FieldConverter$4.convert(FieldConverter.java:114)
> org.eclipse.jnosql.mapping.document.DocumentEntityConverter.lambda$feedObject$5(DocumentEntityConverter.java:160)
I noticed that the META-INF/services has changed in the
"jnosql-communication-core":
https://github.com/eclipse/jnosql/tree/main/jnosql-communication/jnosql-communication-core/src/main/resources/META-INF/services
https://github.com/eclipse/jnosql/tree/1.0.0-b4/communication/communication-core/src/main/resources/META-INF/services
from "jakarta.nosql.ValueReader" to
"org.eclipse.jnosql.communication.ValueReader".
Does this mean that I cannot use "jakarta.nosql.ValueReader" anymore?
Is there any other way to provide a "standard" (without using
"org.eclipse.*") custom serializer/deserializer?
Kind regards,
Dmitry
P.S. I confess that with so many changes between b4 & b5 I am a bit lost :-)
_______________________________________________
nosql-dev mailing list
nosql-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/nosql-dev
--
Otávio Santana
--
Otávio Santana
--
--