Otávio Santana

That is nice @dearrudam You can create draft if you wish, so everyone can check the status in live.

Yes, we can explore any observability of annotations. I mean, given an annotation, we can fire events, thus, the provider can procedure as they wish with this information.

Some suggestions: * JNoSQL with Microprofile integration * JNoSQL with Jakarta EE integration * JNoSQL with JSF * JNoSQL Jakarta MVC * JNoSQL with Websocket * JNoSQL with Bean validation...

one by database we already have here: https://github.com/JNOSQL/demos-se It would be great if we had more integration servers among Jakarta EE techs. About the templates, I like it!

It is a considerable discussion and requires debates like this. As with any topic, we are talking about trade-offs. While the proposal to eliminate the need for the @Column annotation...

> But I wanted to mentioned it, because with a JPA background I was used to drop the annotations where it is not needed :) And this point is super...

Hey @eliasnogueira Check your latest PR: https://github.com/eclipse/jnosql/pull/369 We're running both Java 17 and 20. Once it is on Eclipse Foundation availability nodes, it takes some time to start to run....

Hey @RuanNunes sorry by the delay: 1) Please update the Eclipse ECA, thus allowing us to move it forward. 2) with the newest version and the compilation improvements, it does...

Thanks, @gmfeinberg. The between was a sample; my point was more the error message.

I will update the Jakarta NoSQL spec about this behavior and I will create a specialization for MongoDB once it does support this kind of capability