Previous problems with FastStringService were primarily with
groovy-json-direct going away in Groovy 3 (as it wasn't compatible
with JPMS restrictions) and groovy-all going away after Groovy 3
(again due to JPMS).
I'll have to investigate a bit more to refresh my memory and be able
to have suggest
Hi Paul,
It appears that if a Fragment has an osgi.serviceloader Capability, the
intention is that the host bundle must have a class that can be service
loaded. The commit at
https://github.com/apache/aries/commit/76f39f2#diff-aed8297fc5209027131b1f54544e00eb7614070832051a29561931ed6b933ab7
seems
Hello Paul,
I've conducted further tests. While the FastStringFactor sometimes works
after multiple application restarts, it's mostly failing. I suspect a
problem with the mediator components. The service loader specification (
https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.loader.
Hi Paul,
I've encountered some issues with the FastStringService. I'm getting an
"Unable to load FastStringService" error and I'm trying to determine the
cause. I vaguely recall having trouble with this class in the past, but I
can't remember the specifics.
Given these problems, I don't think thi
Hello Per,
If I understand your problem correctly I have a solution for you. It will
however not work for cloud deployment!!
In a project a long time ago we setup what we called **-platform. This was a
JEE app. The ** was the company name. In that folder we put a subforlder for
deployments. We
