Hi there,
I ran a docker scan on a Fuseki Jena 4.3.2 image which I built with the
latest version:
https://repo1.maven.org/maven2/org/apache/jena/jena-fuseki-server/4.3.2/
This image still contains log4j vulnerabilities fom version 2.16.0.
These are supposed to be fixed in version 2.17.1
I also ha
Hi all,
I created a new jena tdb2 database and loaded it with 256 million triples
in a named graph, using a fuseki2/tdb2 4.3.2 docker setup.
The data also consist of geometries so I built a new docker image based on
jena-fuseki-geosparql 4.3.2
When I bring up the new fuseki container it seems I ca
, TDB2: true
fuseki| [2022-02-01 17:08:15] INFO GeoSPARQLOperations :: Applying
GeoSPARQL Schema - Started
fuseki| [2022-02-01 17:08:15] INFO GeoSPARQLOperations :: GeoSPARQL
schema not applied to empty graph: default
Op di 1 feb. 2022 om 18:13 schreef Erik Bijsterbosch <
e.bijste
at org.apache.jena.fuseki.geosparql.Main.main(Main.java:64)
For that we'll checkout the recommendations here first:
https://sis.apache.org/epsg.html
Op wo 2 feb. 2022 om 09:33 schreef Andy Seaborne :
>
>
> On 01/02/2022 17:13, Erik Bijsterbosch wrote:
> > Hi all,
>
herlands - onshore, including Waddenzee, Dutch Wadden Islands
and 12-mile offshore coastal zone."],
BBox[50.75, 3.20, 53.70, 7.22],
Id["EPSG", 28992, "9.9.1", URI["urn:ogc:def:crs:EPSG:9.9.1:28992"]],
Remark["Replaces Amersfoort / RD Old (code 28991)."
The work around from https://sis.apache.org/javafx.html
Op do 3 feb. 2022 om 19:46 schreef Erik Bijsterbosch <
e.bijsterbo...@gmail.com>:
> Hi Andy,
>
> We advanced a few steps but now we're having trouble using the (full)
> geodetic EPSG dataset.
>
> $ docker-compos
hreef Erik Bijsterbosch <
e.bijsterbo...@gmail.com>:
> The work around from https://sis.apache.org/javafx.html
>
> Op do 3 feb. 2022 om 19:46 schreef Erik Bijsterbosch <
> e.bijsterbo...@gmail.com>:
>
>> Hi Andy,
>>
>> We advanced a few steps but now
-classpath
${SIS_HOME}/lib/:"${FUSEKI_DIR}/${FUSEKI_JAR}":${SIS_HOME}/lib/derby-10.14.2.0.jar
org.apache.jena.fuseki.geosparql.Main "$@"`
echo ${START}
exec ${START}
Op vr 4 feb. 2022 om 09:54 schreef Erik Bijsterbosch <
e.bijsterbo...@gmail.com>:
>
> We successful
Hi,
When embedding geosparql as an assembler in my *fuseki-server *configuration
I get the following error at startup in my docker log:
⠿ Container fuseki-1 Removed0.9s
[+] Running 1/1
⠿ Container labs-services-fuseki-1 Created 0.1s
Attaching t
re:sis-referencing
> org.slf4j:jul-to-slf4j
> org.locationtech.jts:jts-core
> org.jdom:jdom2
> org.apache.commons:commons-collections4
>
>
> We hope to have a version of the Fuseki UI for query and data upload,
> without the admin controls, which can be added to any Fuseki Mai
riple dataset.
Maybe someone can provide me with a way to debug this...
Regards,
Erik
Op vr 11 feb. 2022 om 06:29 schreef Adrian Gschwend :
> On 10.02.22 22:18, Erik Bijsterbosch wrote:
>
> Hi Erik,
>
> > I pursued my attempt to set up a dockerised fuseki-server and
>
aybe it's
> a memory issue?
>
> On the other hand, do you really need the inferences computed for the
> GeoSPARQL schema? If not, it's possible to disable it in the assembler
> file.
>
> On 11.02.22 10:08, Erik Bijsterbosch wrote:
> > Hi Adrian,
> >
Hi,
I want to resolve the transaction error I mentioned before in an earlier
post/conversation.
This question was cluttered too much with context to get noticed, I guess.
So here's a new attempt...
After starting a (4.4.0 docker) fuseki server or a fuseki geosparql server
with inference enabled
he TX abort error is not explicit enough and is thrown as
a general exception handler
I'm not a java programmer, so I hope someone will have a look at this.
Regards,
Erik
Op ma 14 feb. 2022 om 10:41 schreef Lorenz Buehmann <
buehm...@informatik.uni-leipzig.de>:
> Hi
>
>
14 matches
Mail list logo
