The default config for statsgrid-bundle has changed and is now part of the code. The default config in portti_bundle is updated to empty config.
Map publishing functionality has been implemented with a bundle called publisher. All current work toward improving the publishing feature has been done on a bundle publisher2. Since the old one is no longer maintained we are forcing an update to any view having the publisher bundle to start using the publisher2 bundle. This shouldn't cause any problems if you are using the standard publisher bundle with no modifications. If you absolutely want to keep the current publisher bundle and will deal with the changes yourself you can add a property to oskari-ext.properties to skip this update:
flyway.1_37_1.skip=true
You might also have ran this kind of update on your environment previously (through sample-module migrations for example). In such case this migration does nothing.
The latest Openlayers 3 doesn't work with IE9 since it lacks for example requestAnimationFrame() function: openlayers/openlayers#4865. A polyfill has been added to published.jsp for browsers <= IE 9.
You might want to do the same for any custom JSP for published maps if you need to support IE 9.
If you have a custom JSP in your Oskari installation you will need to modify it a bit:
Custom JSPs may have links to Oskari css and have global variables set for Oskari:
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/css/icons.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/css/forms.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/css/portal.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/css/overwritten.css"/>
<script type="text/javascript">
var ajaxUrl = '${ajaxUrl}';
var viewId = '${viewId}';
var language = '${language}';
var preloaded = ${preloaded};
var controlParams = ${controlParams};
</script>
These can be replaced with the following:
<link
rel="stylesheet"
type="text/css"
href="/Oskari/resources/css/forms.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari/resources/css/portal.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/icons.css"/>
<link
rel="stylesheet"
type="text/css"
href="/Oskari${path}/css/overwritten.css"/>
<script type="text/javascript">
var ajaxUrl = '${ajaxUrl}';
var controlParams = ${controlParams};
</script>
Note that you need to remove any references to these globals (language, viewId, preloaded) in index.js as well (in the frontend)
See https://github.com/nls-oskari/oskari/blob/master/ReleaseNotes.md#Default-iconsets-for-applications for more details on frontend changes.
You should also remove any links to oskari_lang_all.js in JSPs as it's no longer generated and its content is included in all of the language files.
There are some improvements in geojson parsing and new methods for parsing WMS/WFS capabilities. Basic oskari-server source is not modified because of this upgrade, only some unit tests.
The configuration has changed for any published maps with toolbar. Automatic migration is done as part of the core migration.
Update IntersectionFeatureCollection2-2.7.1.jar in your webapps/geoserver/WEB-INF/lib directory. Build updated version in https://github.com/nls-oskari/oskari-server/tree/master/geoserver-ext/wps. This is improvement for analysis Geometry clip method.
A new publisher template has been added: content-resources/src/main/resources/json/views/ol3-publisher-template-view.json. This can be inserted to database and configured as a publish template in oskari-ext.properties to use Openlayers 3 as the map-engine for published maps:
view.template.publish=[view id]
This will affect all new maps that are published after the change. The previous ones will remain the same. If a view that is published earlier is edited and saved it will use the new publish template.
The sample application replaces publisher bundle with a refactored version named publisher2. This needs metadata to be generated for appsetups/views created with the original publisher. The sample flyway module has an example (flyway/sample/V1_0_5__publisher2_migration.java) how to make the switch in your application when you are ready. The script generates the metadata from existing published views and replaces the publisher bundle with publisher2 on all views which have the original publisher.
In older Oskari instances users might have saved views that still reference old bundles: mapwfs and featuredata. Views of type USER (portti_view.type) that have these (others shouldn't have them anyways anymore) are automatically updated to replace these with the current implementations. The code for these outdated bundles have been removed from Oskari frontend code a while ago so we need to remove references to them so the personalized default view can work properly.
Old saved views (that users can save) have the bundle setup that was used when the view was saved. Bundles added to default view after the view was saved are not part of those views. This results in personalized default views not having all of the functionality that is available in the default view. A workaround for this is for the user to click the saved view so the application state is changed based on the view and then save the current view as a new one. Then use the new view as the personalized default and delete the old saved view. To update all views of type USER to current bundle setup automatically, there is an example upgrade script in the sample flyway module (flyway/sample/V1_0_6__upgrade_saved_views_to_include_default_view_bundles.java). This update is not forced since some Oskari installs might have used the USER-typed views for other purposes than views saved by users.
Update sld_muutos_n1.sld in Geoserver Styles (updated file in \oskari\oskari-server\content-resources\config\geoserver\data\styles)
Flyway checksum validation fails if line-endings change in files for example between development environments: flyway/flyway#253. To work around this, oskari-ext.properties can be used to autorepair the checksums:
db.flyway.autorepair=true
The servlet-map module has been replaced with spring-based packaging. This uses servlet 3 webapp initialization without web.xml. If you are using the Jetty-bundle downloadable from oskari.org. Add this row to {JETTY_HOME}/start.ini. Take a look at the new Jetty-bundle for example:
etc/jetty-annotations.xml
HTML-loading and action route handling has been separated with HTML response coming from the root path (/) and action routes are now handled with path /action. This propably requires a change in oskari-ext.properties for the property:
# url path to call for ajax requests/action routes
oskari.ajax.url.prefix=/action?
The Maven artifactId was changed to clearly signal the change:
<groupId>fi.nls.oskari</groupId>
<artifactId>servlet-map</artifactId>
As the updated geotools version has dropped Java 6 support, Oskari now requires Java 7 as well.
Keep your current Geoserver data dir as is Replace your geoserver directory under webapps with geoserver dir in jetty-package http://oskari.org/build/server/jetty-8.1.16-oskari.zip
- Current Geoserver build is against Geotools 13.1
- know issue: RYSP WFS parser is not working and partly WFS transport tests fails, if older version of geotools is in use
Routesearch bundle has been moved from under framework to paikkatietoikkuna. Bundlepaths in db need to be updated. Run the node.js upgrade scripts under content-resources/db-upgrade:
SCRIPT=1.29/01_update_routesearch_bundle_bundlepath node app.js
SCRIPT=1.29/02_update_routesearch_bundle_view_bundlepath node app.js
Run on oskaridb:
content-resources/src/main/resources/sql/upgrade/1.29/01_update_defaults.sql
Create new table ( oskari_wfs_parser_config) for WFS 2.0.0 initial parser configs and insert initial values
content-resources/src/main/resources/sql/upgrade/1.29/02_create_oskari_wfs_parser_config.sql
Now builds transport.war instead of transport-0.0.1.war as this is the default Oskari frontend uses.