For the record, I am not saying this change is good or bad. However, no
one responded to my feedback which doesn't feel like community consensus to
me. No vote was taken, it was just done how Carsten wanted it to be done.
Regards,
Eric
On Thu, Jan 11, 2024 at 6:10 AM Robert Munteanu wrote:
>
For the record:
- starting with
https://github.com/apache/sling-org-apache-sling-starter/commit/31e6d31de2ddbb740b553c9c6775e021b5b1d57b
we are using our own Johnzon wrapper, which does not need the SPIFly
mediator
- the SPIFly mediator is still present as it's needed by the Groovy
bundles
Hi Carsten,
For me, requiring a service loader mediator isn't a deal breaker. There
are other parts of my projects that already require it to be there. The
configuration setup is a one time thing and the runtime overhead appears to
be insignificant.
For example,
1. Jetty - The "light"
I think the downside of all of these solutions is that they all require
service loader support - which drags in a lot of other stuff.
We should try to convince the johnzon community to remove the hard
requirement on serviceloader - it doesn't really make sense in this
case. and then we would
Is the johnzon 2.x implementation better than the parsson library that we
are already including in the starter?
I've just been switching the geronimo-json_1.0_spec and johnzon-core
dependencies to these:
jakarta.json
jakarta.json-api
2.1.1
