Good point. I'll start a new thread focused on Tomcat.
On 4/10/24 10:24, Jacques Le Roux wrote:
Le 10/04/2024 à 09:45, Florian Motteau a écrit :
Sure, I just question the fact that this important discussion
(updating tomcat, which leads to a lot of work/implications) occurs
via a remote task.
Le 10/04/2024 à 09:45, Florian Motteau a écrit :
Sure, I just question the fact that this important discussion (updating tomcat, which leads to a lot of work/implications) occurs via a remote task.
It may need its own thread (updating tomcat : yes ? no ? why ? how ? people insights about this
Le 10/04/2024 à 09:03, Gaetan a écrit :
Hi Florian ! Thanks for the answer
I agree that migrating Tomcat isn't mandatory for the initial task. It
just feels cleaner that way, so that we don't have two http servers
running in the framework. But it made me think that OFBiz would have
to
Hi Florian ! Thanks for the answer
I agree that migrating Tomcat isn't mandatory for the initial task. It
just feels cleaner that way, so that we don't have two http servers
running in the framework. But it made me think that OFBiz would have to
migrate at some point.
> updating Tomcat is no
Hi Gaetan,
I would ask if using the prometheus java client's embedded http server
is such a bad thing that we need to update OFBiz Tomcat and face the
huge consequences of this update. I'm not fully aware of all the
implications here, but my 2ct would be to reconsider this point, because
Hi everyone. I'm working on UEL engine migration (OFBIZ-12991 [1]).
Why ?
It starts from the idea of creating a Prometheus plugin, allowing to
expose data to grafana. There is a lib that exists in java. [2]
This lib comes with an integrated httpserver but it would be much
cleaner to use the
