Emanuele Tajariol ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5f715f5e-d477-4c0d-97bb-5b7644324d82
 ) *created* an issue

GeoServer ( 
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 ) / Task ( 
https://osgeo-org.atlassian.net/browse/GEOS-9897?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 ) GEOS-9897 ( 
https://osgeo-org.atlassian.net/browse/GEOS-9897?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 ) JTS upgrade breaks geofence integration ( 
https://osgeo-org.atlassian.net/browse/GEOS-9897?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 )

Issue Type: Task Affects Versions: 2.17.3, 2.18.0, 2.18.1, 2.17.4, 2.18.2 
Assignee: Emanuele Tajariol ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5f715f5e-d477-4c0d-97bb-5b7644324d82
 ) Components: GeoFence Created: 10/Feb/21 4:24 PM Environment:

GeoServer >=2.17.3
geofence-server with postgis backend

Priority: High Reporter: Emanuele Tajariol ( 
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=557058%3A5f715f5e-d477-4c0d-97bb-5b7644324d82
 )

Since 2.17.3 JTS has been upgraded to 1.17.0
JTS 1.17 breaks API compatibility (see 
https://github.com/locationtech/jts/blob/master/doc/JTS_Version_History.md#api-changes-1
 )
This break happens within the postgis driver for hibernate spatial 1.1.3.1 used 
by GeoFence.
This means that if GeoFence runs as a standalone webapp, the JTS version will 
be the one declared within the GeoFence deps and everything will work. When 
GeoFence is run within GeoServer, it will use the GeoServer version, and 
hibernate spatial will break.

A new version of hibernate spatial (1.1.3.2) has been built with support to JTS 
1.17.
Since GeoServer 2.17.x relies on GeoFence 2.4.6, a new release (2.4.6.1) has 
been done, using the updated hibernate-spatial version.

Version 2.18 will use the 3.4.6 as well, since next version brings in some 
changes in DTOs (SRID and areas)
Version 2.19 is using a geofence version that supports the SRID and area 
changes.

Pls also refer to https://github.com/geoserver/geofence/issues/166

( 
https://osgeo-org.atlassian.net/browse/GEOS-9897#add-comment?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 ) Add Comment ( 
https://osgeo-org.atlassian.net/browse/GEOS-9897#add-comment?atlOrigin=eyJpIjoiMDMyMTRhOTIwNmVhNDc2MmJmNWU3NjMzYTlkMTA4MWMiLCJwIjoiaiJ9
 )

Get Jira notifications on your phone! Download the Jira Cloud app for Android ( 
https://play.google.com/store/apps/details?id=com.atlassian.android.jira.core&referrer=utm_source%3DNotificationLink%26utm_medium%3DEmail
 ) or iOS ( 
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailNotificationLink&mt=8
 ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100154- 
sha1:7cdb571 )
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to