Patch: JMap 6.0 k is now available

Created by Sylvain Beaumont (Unlicensed)
Last updated: Oct 08, 2015
3 min read

The 6.0 k 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 (6.0 a-j). 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 k patch. See at the end of the release notes for more details.

JMap 6.0 k release notes
  New features / improvements
- API change: new methods were added into editable spatial data sources to allow custom id generation.
- The loading of attribute queries was optimized in JMap Pro.
- JMap Web now displays an "Unsupported Browser" message for unsupported browsers (IE8).
- The filter defined in the spatial data source list is now maintained in JMap Admin.

  Bug fixes
- The SQL Server spatial data source didn't fully support empty geometry collections.
- Layers loaded by reference kept their status "ready" whereas source layers had been deleted.
- JMap Server didn't fully support BLOB attributes.
- Fixed a crash while reading invalid block references in the DWG/DXF reader.
- The ev() function used in the layer mouseover didn't work when the attribute name had accentuated characters.
- Fixed a problem with the ev() function when the id attribute was used in an external database data insertion.
- The ifNotNull() function didn't work correctly when combined with the format function() in the mouseover configuration.
- Fixed attribute queries loading and execution on chained layers loaded by reference.
- Form component lists were not fulfilled on some referenced layers.
- External attribute values couldn't be used in external database forms and subforms.
- Group by clauses were not supported in the external attributes configuration.
- The mouseover crashed in JMap Web when the sessionId() function was used.
- The username() function was not supported by layer forms in JMap Web.
- Fixed the measure label location when the space bar was used to finish the measurement in JMap Web.
- JMap Pro applications deployed as Java Web Start applications could not be executed by Google Chrome 45.
- The processing of overlapping elements was optimized at the reception of requested tiles in JMap Pro.
- A "LayerSelChangedEvent" was fired from layers loaded by region on all zoom changes in JMap Pro.
- Geometry information and measurement tools were not displaying the same results in JMap Pro.
- It was not possible to open a PDF document linked in layer metadata displayed in JMap Pro.
- Fixed the selected elements count displayed after the execution of a spatial query.
- Fixed missing Spanish translations in JMap Pro for spatial queries.
- Fixed information reports on WMS layers that used the "application/vnd.google-earth.kml+xml" encoding format.
- WMS information reports using the vnd.ogc.gml format was not displayed correctly in JMap.
- Fixed a problem while adding project permissions to a user that was not visible in the current page in JMap Admin.
- While editing a symbol of a point layer, the symbol was always reset to the default one in JMap Admin.
- It was not possible to configure the label position with Google Chrome in JMap Admin.
- Changes made to spatial data source metadata changed values for all metadata based on the same template.
- Fixed compatibility problem with IE 11 while importing spatial data sources in JMap Admin.
- Fixed rendering issues in the form display order dialog in JMap Admin.
- The offline mode could not be defined for layers while deploying a JMap Mobile application.

  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