On 20/10/2025 11:26, Sorin Gheorghiu wrote:
Hi Rob,
thanks for answering, we use Tomcat in production because it works
better then the standalone server and we are happy with its limited
customised status.
Hi Sorin,
In what way does it work better?
Andy
Regards,
Sorin
Am 20.10.2025 um 10:40 schrieb Rob @ DNR:
Sorin
You have two options:
*
Run it in the standalone server form, this used embedded Jetty and you
can provide full Jetty configuration files if you need deep
customisation of the Jetty server setup. This is what most users run.
*
Use the same Fuseki dependencies that the fuseki-server module does
and build your own custom WAR file with the Fuseki features you need.
As Andy noted the WAR packaging is very limited in its ability to be
fully customised in the same way as the standalone server can be.
Rob
From: Sorin Gheorghiu<[email protected]>
Date: Monday, 20 October 2025 at 08:28
To:[email protected] <[email protected]>
Subject: Re: [ANN] Apache Jena 5.6.0
Hallo Andy,
Thank you for the reply.
I currently use the WAR file to run Fuseki in Tomcat, but do I
understand correctly this will not be supported in Jena 6. How to run it
then?
Regards,
Sorin
Am 17.10.2025 um 18:42 schrieb Andy Seaborne:
On 17/10/2025 08:58, Sorin Gheorghiu wrote:
Hello Andy,
will Fuseki being removed in Jena 6?
No.
jena-fuseki-server is the code that goes to the file in the fuseki
download as "fuseki-server.jar".
This is servlet form of Fuseki with additional configurable features
in Fuseki modules.
This has been since 5.3.0 and has been the focus of fuseki development
for awhile.
* Retire the Fuseki WAR file, jena-fuseki-webapp, jena-fuseki-war
This are Fuseki packaged as WAR (= webapp).
This is an inflexible packaging and provides no advantage when running
a single server in an OS process.
It has not been receiving the newer feature of Fuseki.
Andy
