Patch: JMap 6.5g is now available

Created by Laurent Boileau (Unlicensed)
Last updated: Sept 26, 2016 by Sylvain Beaumont (Unlicensed)
4 min read

The 6.5g patch is now available for download on our website: http://k2geospatial.com/support.

Take note that this patch is only compatible with JMap 6.5 and its patches (a-f). If you are using a version prior to 6.5, your JMap Server must be migrated to version 6.5 before installing this patch. After installing this patch, all deployed applications must be updated in JMap Admin.

For your information, a complete version of JMap 6.5 that contains all released patches is now available for download on our website. That complete version can be installed on all JMap versions starting from JMap 6.0.

Note: JMap 6.5g is compatible with our new version of JMap Web (7.0 preview). It must be installed separately and is available on our web site (http://k2geospatial.com/support).

JMap 6.5g release notes

New features / improvements

- Optimized the loading of layers loaded by reference from a remote JMap Server.
- Long text values read from files are now truncated to the database field length instead of crashing while updating a spatial data source.
- Added a system administration request to launch a spatial data source update.
- Added a system administration request to get spatial data sources information.
- It is now possible to force a default application language in JMap Web applications.
- The layer style sample was improved for custom strokes in JMap Admin and JMap Pro.
- Added support for the "NAD83 / MTQ Lambert" projection.

Bug fixes

- Added more robustness in JMap Server to prevent crashes while requesting layers at the project initialization.
- Spatial data sources now get an error status if any error occurs while initializing the data manager at the JMap Server startup.
- Fixed an issue while editing elements in the WKB spatial data source if the JMAP_ID attribute was bound into the related layer.
- It was not possible to update geometries in the JMap editable spatial data source if the MODIFICATION_TIME attribute was bound into the related layer.
- Database connection pools could use more resources than the specified maximum limit.
- The pool maximum limit had to be greater that the initial size while configuring database connection pools.
- The JMap Server image producer didn't allow creating images smaller than 10x10 pixels.
- Changed the JMap Server image producer to allow only the WMS service to render images having different X/Y scales.
- Exception stack traces could be missing from JMap log files.
- Users with JMap Admin permissions could remove any users from permissions lists.
- Fixed the rendering of the permissions report page with long layer names in JMap Admin.
- The DB user manager configuration page now uses the connection pool schema by default to speed up the rendering with Oracle.
- JMap Admin didn't give any feedback when a layer style was deleted.
- Spatial data source metadata were not exported with the JMap configuration.
- Unpublished layers were available while deploying JMap Web and JMap Mobile applications.
- The "Allow additional levels" option value was lost while editing deployed JMap Web applications.
- Fixed the map extent that was invalid after having updated coordinates in the JMap Web's geographic properties configuration page.
- Fixed authentication issues in JMap Admin while managing the GeoWebCache zip data file for the JMap Mobile application.
- The language used in the JMap Admin's viewer didn't match the language selected in JMap Admin.
- The "Copy data" permission was checked for raster layers in the permissions report.
- Fixed a crash while creating a style template for JMap administrators who didn't have the required permissions.
- Elements and annotations were missing from the printed map in JMap Web.
- The mouseover's host() function returned the JMap Server's loopback address in JMap Web.
- It was not possible to load and execute two JMap extensions in JMap Web.
- External database forms failed to load in JMap Web if no layer attribute form was defined.
- Fixed a crash while calling the isEditable() method on a vector layer loaded by reference in JMap Pro.
- Fixed an issue with the scale and the paper orientation while changing layouts in the print dialog in JMap Pro.
- Fixed an incoherent option related to personal layers while creating or saving a JMap context in JMap Pro.

JMap Web 7 (preview 3)

- Tile images stopped loading when Google Street View was used in Microsoft Edge.
- Google Street View stopped refreshing the current position after a window resize.
- Elements and annotations were missing from the printed map.
- Added support for long layer names in the layer bar.
- The JMap logo could overlap the Google logo on the map.
- Attribute query groups were not sorted alphabetically.
- The map overview included configured layer overlays.
- The map overview was blank if the base layer was not provided by JMap Server.
- The drop down menu didn't display while typing an address in the Google Directions form.
- The starting and arrival point images didn't display on the map.