forked from deegree/deegree3
-
Notifications
You must be signed in to change notification settings - Fork 2
Upgrading deegree webservices
Torsten Friebe edited this page Jun 7, 2024
·
26 revisions
NOTE: Before upgrading to version 3.6 install the latest version of 3.5 (at least 3.5.7)!
- Requires Java 17
- Requires Java Servlet API 6.0 compliant container (e.g Apache Tomcat 10.1+)
- Requires PostgreSQL 16.0+
- Requires PostGIS 3.4+
- Issue #1616/PR #1708: Requires change of the password format stored in console.pw file used by the deegree admin console.
- TBD
NOTE: Before upgrading to version 3.5 install the latest version of 3.4 (at least 3.4.31)!
- Requires Java 11
- Issue #1495/PR #1496: The XML schema location has been changed. To enable code completion for the last available feature set within your IDE while editing the deegree configuration files you have to change the schema location to https://schemas.deegree.org/core/3.5/.
-
Issue #1017/PR #1337: Requires changes to all JDBC database connection files using Apache DBCP:
- the
driverClassName
changed fromorg.apache.commons.dbcp.BasicDataSource
toorg.apache.commons.dbcp2.BasicDataSource
(Notice the 2 in the package namedbcp2
!) - the
maxActive
configuration option has been renamed tomaxTotal
- the
maxWait
configuration option has been renamed tomaxWaitMillis
- the
removeAbandoned
configuration option has been replaced byremoveAbandonedOnBorrow
andremoveAbandonedOnMaintenance
- the
- Issue #1157/PR #1441: Syntax of ehcache configuration changed
- Issue #1102/PR #1442: deegree no longer sends a version header by default in HTTP response.
- Issue #1494/PR #1489: for protecting deegree's REST API against un-authorized access use the HTTP header or parameter instead of BASIC HTTP Authentication.
- ensure that the PostgreSQL database used for SQLFeatureStore with BLOB mode have the
SRID
set.