Patch: JMap 6.5 a is now available

The 6.5 a 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.5. 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 having install this patch, all deployed applications must be updated in JMap Admin.

JMap 6.5 a release notes
  New features / improvements
- Changed print templates to always print using the selected map in JMap Pro.
- The loading of attribute queries was optimized in JMap Pro.
- The processing of overlapping elements was optimized at the reception of requested tiles in JMap Pro.
- Improved the layer label frames rendering in JMap Pro.
- JMap Pro API change: new methods were added into editable spatial data sources to allow custom id generation.
- Added support for dynamic layers in JMap Web.
- Added a circular measurement tool in JMap Web.
- Added a filtering API in JMap Web.
- A layer filter was added to the layer bar in JMap Web.
- Elements found by attribute queries are now displayed as selected on the map in JMap Web.
- It is now possible to choose the working layer for selection in JMap Web.
- A clear text button was added to form text fields in JMap Web.
- Improved the display of measurement tools in JMap Web.
- Improved the display of the itinerary returned by the Google Maps itinerary tool in JMap Web.
- 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.
- It is now possible to activate the blinking mode for layer styles in JMap Admin.
- WMS services deployed in JMap Server now close JMap sessions automatically after each requests.
- Added debug logs while extracting elements in the SQL Coordinates spatial data source.

  Bug fixes
- Fixed attribute queries loading and execution on chained layers loaded by reference.
- Form component lists were not fulfilled on some referenced layers.
- Fixed individual thematics compatibility issues between 6.5 and 6.0 for referenced layers.
- Fixed an error that occurred when a referenced layer with a thematic that contain no value was loaded.
- Users could 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.
- Layers loaded by reference were not displayed when the local project didn't have the same projection as the remote project.
- Remote raster spatial data source projections were always set to Unknown in the configuration wizard.
- The SQL Server spatial data source didn't fully support empty geometry collections.
- Fixed a crash while reading invalid block references in the DWG/DXF reader.
- Invalid complex elements read from a DWG file could crash the map rendering.
- JMap Server didn't fully support BLOB attributes.
- Fixed support for WMS GetMap queries on point layers having a width or a height of 0.
- The Enterprise Geodatabase spatial data source didn't support data outside the sde schema.
- Added a filter to list useful tables only in the Enterprise Geodatabase spatial data source configuration page.
- Added robustness for coded domain values in the Enterprise Geodatabase spatial data source.
- 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.
- WMS layer reports were not translated.
- Fixed authentication issues when the controlled access was activated in deployed WMS services.
- Fixed a problem with labeling which caused crashes while printing a map.
- Script processing in the layer mouseover could remove the last character of the output text.
- The ev() function used in the layer mouseover didn't work when the attribute name had accentuated characters.
- The ifNotNull() function didn't work correctly when combined with the format function() in the mouseover configuration.
- It was not possible to open a PDF document linked in layer metadata displayed in JMap Pro.
- The dynamic option for thematic legends could stop working properly in JMap Pro.
- The selection explorer content was invalid after the execution of a spatial query in JMap Pro.
- It was possible to select a different symbol for proportional thematics minimum and maximum styles in JMap Pro.
- Fixed a problem with layer visibility checkboxes in the hierarchy bar when multiple views were used.
- 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.
- Geometries location could be saved at the wrong location following a JMap Pro/Mobile/Web transaction if the layer's offset had changed.
- Updated geometries could be displayed at the wrong location after a spatial data source update in JMap Web.
- Checkbox components from layer forms in JMap Web were not set properly.
- Fixed a problem while unselecting elements in JMap Web when the base layer had changed.
- The result layer was not always visible after the execution of an attribute query in JMap Web.
- Fixed a crash while processing empty date and timestamp values from edition forms in JMap Web.
- Fixed an error that occurred when the element id attribute was defined in the layer attributes form in JMap Web.
- The initial extent defined in the JMap Web application deployment was not respected by the application.
- The map disappeared when a layer was edited and the GeoWebCache was used in JMap Web.
- Base layer thumbnails were not always displayed in JMap Web's layer bar.
- Fixed the display for long layer names in the JMap Web's layer bar.
- The layer form list is not more displayed when only one form is defined in JMap Web.
- The mouseover crashed in JMap Web when the sessionId() function was used.
- Fixed a problem while adding a new element in JMap Web when the id field type of the related spatial data source was a 4 bytes integer.
- The JMap session could expire in JMap Web while the HTTP session was still valid.
- Fixed support for attribute queries without constraint in JMap Web.
- Fixed a crash in JMap Web occurring while printing maps with some drawn annotations.
- While displaying information reports, switching from an advanced to a basic report would remove the map image from the advanced report.
- The help menu in JMap Pro still pointed to the JMap 6.0 user manual.
- A crash occurred while creating a new external attribute query in JMap Admin.
- Group by clauses were not supported in the external attributes configuration.
- The deployed application list was taking a long time to display when the "Owners" column was displayed in JMap Admin.
- Vector layer translation had no effect if the layer map unit was degree.
- Vector layer generalization had no effect if the layer map unit was degree.
- It was possible to bypass the security of the user manager page in JMap Admin by writing the URL in the browser.
- Super administrators could not edit a project if they were not their owner.
- Super administrators could access a project if they didn't have explicit permissions defined.
- Super administrators could not edit attribute queries if they didn't have explicit administration permissions.
- All administrators could give administration permissions to users in JMap Admin.
- Fixed a problem while adding project permissions to a user that was not visible in the current page in JMap Admin.
- Enterprise Geodatabase spatial data sources were not exported nor imported with the server configuration.
- Fixed administration permissions importation issues while importing a configuration from JMap 6.0.
- Remote access permissions in spatial data sources were lost after a migration from JMap 6.0 to JMap 6.5.
- When importing projects, the EPSG code was duplicated in the project and spatial data source lists.
- Exporting a server configuration over an existing exportation file changed the file name and location.
- Added a validation on the initial view bounds computed after a project reprojection.
- Added more robustness while importing invalid initial view bounds from previous versions.
- Fixed a crash while creating a vector JMap Server spatial data source in JMap Admin.
- The offline mode could not be defined for layers while deploying a JMap Mobile application.
- Added more robustness when the access control list related to a deployed application was manually deleted.
- Spatial data sources created in older versions (4.0 and previous) of JMap could display an invalid projection name.
- The delete button from the layer summary page didn't work if the layer used some scripts in its configuration.
- Validation messages for attribute queries edition didn't follow JMap Admin standards.
- Fixed the alignment of the layer forms display order configuration page in JMap Admin.
- The displayed deployed application type could be invalid after restarting JMap Server.
- Fixed many Spanish translations in JMap Admin.

Documentation:

Installation guide

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

Sylvain Beaumont
Director, Research and Development
K2 Geospatial