Patch: JMap 6.0 l is now available

The 6.0 l patch is now available for download on our website: http://k2geospatial.com/en/products/downloads.

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

Warning: if your organization customized a JMap Pro application template and you are updating a version prior to 6.0 i, a minor change must be made to your template after having installed the 6.0 l patch. See at the end of the release notes for more details.

JMap 6.0 l release notes

  New features / improvements
- Changed print templates behavior to always print using the selected map in JMap Pro.
- The JMap license agreement was updated in JMap Admin and in the JMap installer.

  Bug fixes
- JMap Pro applications deployed as Java Web Start applications could not be executed by Google Chrome 45.
- Fixed an error that occurred in JMap Pro while loading attribute queries if the connection was offline.
- The dynamic option for thematic legends could stop working properly in JMap Pro.
- Fixed a problem with labeling which caused crashes while printing a map in JMap Pro.
- It was not possible to add a custom button for a layer in the layer bar in JMap Pro if metadata were available on that layer.
- Fixed a compatibility issue with Google Maps configured as base layers in JMap Web.
- Fixed attribute queries loading on some layers loaded by reference.
- Users couldn't open reports belonging to referenced layers if they didn't also had access permissions to the remote project.
- Layers loaded by reference kept their status "ready" whereas source layers had been deleted or had an error status.
- Invalid complex elements read from a DWG/DXF file could crash the map rendering.
- The arrow head was missing from MLEADER entities read in DWG/DXF files.
- Fixed a layer hierarchy refresh problem in JMap Admin that occurred when the name filter was filled.
- An error message is now displayed in JMap Admin if GML files dependencies can't be loaded in the spatial data source wizard.
- The spatial buffer operation generated a polygon that was not valid in SQL Server.

  Change
- If your organization customized a JMap Pro application template and you are updating a version prior to 6.0 i, you will need to edit the "dependencies" file located in the root folder of your custom application.

Change the following line using a text editor:
${JMAP_HOME}/lib/poi.jar
to
${JMAP_HOME}/applications/lib/poi.jar
and then redeploy your applications.

--------------------------------------------------

Sylvain Beaumont
Director, Research and Development
K2 Geospatial