What's New 2.5

2.5.28.11, 2.5.29.7, 2.5.30.4

Released 28 November 2019

Fixes

• Street View panel fix

  • Resolved an issue with moving in the street view panel bouncing back at certain locations which was stopping users from being able to move forward in the street view panel.

2.5.30.3

Released 20 November 2019

Fixes

• List-box/combo-box field issue

  • Some field functionality in 2.5.30 changed the way list-box and combo-boxes worked by default, this update fixes the fields so they work more like they did before 2.5.30.

2.5.30.2

Released 13 November 2019

Fixes

• ToC model parsing issue

  • When generating an id for a toc model group entry that does not have an id set the generation of the id required a map engine to be know which may not always be the case, this would result in the toc model not being available. This update resolves the requirement to have a mapengine specified and will generate the id without one.

2.5.30.1

Released 12 November 2019

Fixes

• Data grid filter fixes

  • Exporting data from the data grid when using a filter would not always work

  • Filtering on a string column was not performing a wildcard search  by default

2.5.30

Released 8 November 2019

This is the final release of 2.5, only hotfixes will be provided for 2.5 releases, any new functionality will be provided in 2.6

Enhancements

• GDA2020

  • Added more support for working with GDA2020

• Grid Export

  • The export will only export the selected records if there are any records selected, otherwise, it will export all rows (as it did before)

  • Work has been done to improve the consistency and availability of filters for all data definition types

• Listbox Fields

  • If a list-box field is marked as required and only has a single value in the list, the value will be pre-selected and the drop-down trigger button is hidden

  • Parameters without allowNewValues set to true will now default to list-boxes, rather than combo-boxes, which changes the functionality of the field, add allowNewValues='true' to any parameters that need to be combo-boxes.

• GeoJSON Content-Type

  • REST API now supports the mime type of application/vnd.geo+json for GeoJSON, as well as application/json

• Enhanced Spatial Filtering

  • ECQL, rather than just CQL, is available in more places throughout the configuration of spatial queries, allowing for more options when creating spatial filters, including in spatial data definitions

• Non-spatial editing

  • A new edit panel is available to help edit related records

• Map API

  • Updated to allow the caller to provide the selection information, rather than always obtaining it from the selection manager, plus some other API enhancements

• ArcGIS HTTPS

  • Improved support for internal ArcGIS services accessed via HTTPS (to work around certificate issues)

• ToC Models

  • There's additional validation performed on ToC models before they're made available. If your client doesn't display a ToC and map after this update, check the weave.log to see why as it's likely to have failed validation

• BIRT Excel Export 

  • Reports exported to Excel format would break up the data into multiple sheets, this has been disabled and all data will be exported into a single sheet

• Support Dump Update

  • Additional files have been included in the support dump

• Spatial Editing

  • Various import improvements

  • Improved support for editing AGS GeoDatabases

• Spatial Upload

  • Improvements in MIF and TAB support

• QGis 3

  • Added a workaround for QGis 3 WMS server bug

• OGR Driver Update

  • The native code for working with OGR data sources has been compiled on an older OS to make it compatible with a wider range of operating systems

• Grid Panel

  • Improvements in cut and paste support

Fixes

• Bookmarks

  • email links not working in Outlook

  • Listing available shared and published bookmarks didn't always list the correct bookmarks

• Image Slider

  • Slider position not updating when map opacity was changed programmatically

  • The slider would sometimes be hidden behind other items

• Grid Export

  • Export was ignoring any filter

• Tooltips

  • Some map tools did not allow for their tooltips to be directly configured in the tool configuration

• ToC Metadata

  • The ToC metadata tool only every used the URL from the first entry, not the one matching the selected ToC entry

• Redline

  • A line with arrowheads that had zero-length would cause problems

• Non-spatial Editing

  • Some fixes to stop the editing state from getting out of sync with the edit input panel

• Indexing

  • A data source with an unsupported CRS would stop the index from being built (it still won't build, but now you'll know why)

  • Index building was processing every 1000th record twice

• Config Processing

  • A minor fix has been applied to the config file reader to help resolve issues with lists that have items that include and don't include the namespace, e.g. <ns:test><a><ns:a></ns:test> should treat <a> and <ns:a> as the same but it wasn't

• Geometry API fixes

  • Sometimes the geometry API's would generate non-valid geometry object

• Fix Chrome Issue

  • Fixed an issue with Google Chrome sending a new format of Accept header

• Admin UI File Explorer

  • Fix to help handle editing of XML files with an encoding other than UTF-8

• WMS Map Engine

  • The WMS map engine would only handle a single top-level layer tag in the capabilities document

2.5.29.6

Released 26 September 2019

Fixes

• Bookmark email issue

  • There was issue when using Microsoft Outlook as your email client when trying to generate an email a bookmark

• Image slider issues

  • Some small issues when image slider have been fixed

• Spatial upload fix

  • The zoom to layer ToC menu option would not work for an uploaded layer if it was uploaded in a projection different from the client

• Health check issue

  • The health check page stopped working in Google Chrome after a recent version update

• Non-spatial editing fix

  • Sometimes the client would not exit editing mode when an edit was submitted or cancelled

2.5.29.5

Released 11 September 2019

Fixes

• Table of Conents metadata issue

  • Only the first URL was being used even if there were multiple metadata entries.

• Tooltip fixes

  • Some map tools could not have their tooltip text set directly in the client configuration.

2.5.27.14

2.5.28.10

2.5.29.4

Released 10 September 2019

Fixes

• Spatial editing fix

  • Updated the previous hotfix to not require that a schema be set in the spatial engine config (which was a requirement for the previous version of the hotfix)

2.5.27.13

2.5.28.9

2.5.29.3

Released 9 September 2019

Fixes

• Spatial editing fix

  • Creating records within Weave in a ESRI GeoDatabase enabled database can stop users being able to create records in ArcMap.

  • Applying this fix could also stop Weave from creating new records too, since it now creates records in the same way as ArcMap, copying the table to a new table and renaming the old and new tables to replace the corrupt one will fix the issue.

  • This fix currently only supports SQL Server and is only required if your database has been enabled for GeoDatabase use.

2.5.28.8

2.5.29.2

Released 26 August 2019

Fixes

• Spatial upload fix

  • Projection files uploaded via the spatial upload weren't always being matched to their appropriate EPSG code resulting in the Zoom to Layer toc action not working

2.5.29.1

Released 22 August 2019

Fixes

• Published bookmark fix

  • Only bookmarks published by the current user are listed as being available

  • Some of the formatting in the Admin UI for bookmarks was not correct

• Redline arrow fix

  • Lines that had zero length and were drawn with arrow heads would not render correctly on the server

• CQL fix

  • Some code that was supposed to support extended CQL queries was not

• Index build update

  • If an index was configured to used a coordinate reference system that Weave doesn't support it was silently ignored

• Spatial edit geometry validation update

  • Geometry validation when submitting an edit was not completely validating the geometry against the underlying table requirements resulting in invalid geometry being allows to be submitteed to the database

2.5.27.12

2.5.28.7

Released 22 August 2019

Fixes

• Spatial edit geometry validation update

  • Geometry validation when submitting an edit was not completely validating the geometry against the underlying table requirements resulting in invalid geometry being allows to be submitteed to the database

2.5.27.11

2.5.28.6

Released 15 August 2019

Fixes

• Combo box fix

  • And update to IE 11 could cause combo boxes to not display any data

2.5.29

Released 15 July 2019

Enhancements

• Bookmark updates

  • Include the selection for the active entity when creating a bookmark

  • Additional management functionality

  • New type of bookmark - Shared Bookmarks, i.e. generate a URL that can be provided to a third party to start Weave and open the bookmark

  • Specify your own folder structure for presenting published bookmarks

  • OSGi console commands to operate on bookmarks

• Spatial edit import update

  • Importing geometry is no longer as strict if the number of geometries in the entity to import doesn't match the restrictions configured in the edit, it will now import as much of the geometry as it can to meet the requirements, e.g. an edit config that says it only supports a single polygon will only import the first polygon if a multi-polygon entity is the source of the import.

• Spatial editing configuration validation update

  • The configuration for spatial edits is now more rigorously checked when the configuration is processed, rather than waiting until an edit is submitted to find problems.

• Spatial editing processing update

  • The way the spatial edits are applied to the database has been updated to provide more control to the Weave code that handles the submission (resulting in improved reliability and performance).

• Spatial edit import update

  • You can also specify that attributes be included (in certain circumstances) when importing, rather than just the geometry.

• Grid panel update

  • More grid panels have the "bring to front" functionality included, beyond just some identify tools, so that they can be made visible if their content is changed.

• Index build update

  • If an index content does not exist when it's created then the index will be built, including at Weave startup.

• ToC metadata update

  • The ToC metadata context menu item is now more flexible in how it can generate the URL used to open the metadata, providing access to more variables when constructing the URL.

• BIRT designer update

  • The BIRT Report Designer is no longer included as part of the main installer and has a separate installer of its own.

Fixes

• Clean up failed index builds

  • Temporary directories should now be removed if an index build fails

• ArcGIS REST spatial engine fix

  • Fixed issue with handling dates/times returned by ArcGIS Online

• ArcGIS REST spatial engine fix

  • Fixed issue with selections not drawing for entities hosted by ArcGIS Online

• ArcGIS REST spatial engine fix

  • Fixed issue with spatial operations not working because the URL sent to ArcGIS Online was too long

• Fix for null table values in BIRT reports

  • If you access data directly from a database in a BIRT report (i.e. not via Weave) and a table row contained a null value, this was not always handled correctly

• Editing errors hidden from log

  • Some edit related errors were not making it to the weave.log file

• Edit config update

  • Configuration for list parameters in an edit allows the administrator to specify that new values are allowed, when in fact the server does not support this

  • Configuration for list parameters in an edit should require that the label and value columns be explicitly specified

• Identify tool highlight fix

  • In some situations the highlighting placed on the map for some identify tools wasn't removing the highlight

• Grid panel pageSize fix

  • Setting a pageSize of 0 on some grid panels resulted in nothing being displayed, rather than the paging being disabled

• Missing data definitions in BIRT Report Designer

  • Data definitions weren't being listed in the Report Designer

• Collapse theme update

  • The arrows on the buttons were not changing direction when the panels were expanded/collapsed for the collapse theme

• Spurious log message removed

  • Fetching geometry from the server would log an error when there was none

• KML fix

  • The KML parser was too strict when checking the version of the KML file to parse, and would reject files even if it could parse them

• Client configuration issue

  • Scales were require to be set when using a tiled ArcGIS map engine, when they didn't need to be

• Mapping fix for Google Chrome

  • The latest release of Chrome can show problems when the map is panned via code

• Combo box fix

  • And update to IE 11 could cause combo boxes to not display any data

2.5.27.10

2.5.28.5

Released 30 May 2019

Fixes

• ArcGIS map engine fix

  • Fixed a problem with the checking of the minScale value when using a tiled ArcGIS map engine.

2.5.27.9 2.5.28.4

Released 21 May 2019

Fixes

• KML upload fixes

  • The KML parsing has been updated to work with a wider range of KML files.

2.5.21.13

2.5.22.11

2.5.23.8

2.5.24.10

2.5.25.4

2.5.27.8

Released 20 May 2019

Fixes

• Latitude/Longitude coord zoom issue

  • The latitude zoomed to with the coord zoom tool when using DMS was incorrect.

2.5.28.3

Released 17 May 2019

Fixes

• Remove spurious log message

  • An error message reporting "Failed to execute statement..." would sometimes be logged, even when things were ok.

2.5.21.12

2.5.22.10

2.5.23.7

2.5.24.9

2.5.25.3

Released 17 May 2019

Fixes

• Latitude/Longitude display issue

  • The latitude reported by the DMS conversion was not always correct.

2.5.28.2

2.5.27.7

Released 16 May 2019

Fixes

• BIRT designer fix

  • Data definition weren't showing up when editing/creating a data set.

2.5.28.1

Released 16 May 2019

Fixes

• Street View and Nearmap fix

  • The Street View and Nearmap panels would not update their position unless the main map was visible.

2.5.28

Released 12 April 2019

Enhancements

• Published bookmark action update

  • The weave.publishedbookmark action is now also available as com.cohga.html.client.map.publishedbookmark, for consistency.

• WeaveLink update

  • The client code for interoperability with WeaveLink has been restructured in preparation for the replacement of the WeaveLink component.

• Redline

  • A new circleByRadius tool is available for the redline toolbar.

• StreetView

  • There is now more control over how the StreetView panel is displayed, more configuration options for the StreetView panel have been exposed.

• Page size enhancements

  • More grid panels now support a pageSize parameter to determine the default number of records to display.

• Map Tips

  • The map tip popup is now smarter about when it decides it has to be hidden, making it a lot easier to embed and access HTML links in the popup.

• Selection identify tool update

  • The weave.selectionIdentify,a.k.a. com.cohga.html.client.map.selectionIdentify, tool now supports entityListWidth, entityListWidthMin and entityListWidthMax to alter the size of the entity list panel.

• Map panel update

  • For tiled map engines you can now directly specify a different set of resolutions for the map engine from that of the client, by setting serverResolutions as an option in the map engine, in the same way that the resolutions are set for the map view.

• Window behaviour change

  • Weave windows are now constrained to the browser window so they can't accidentally be moved outside of the browser and lost.

• New popup plugin

  • The map now supports a new map tips plugin: Client Plugin Map Popup.

• Connection monitoring enhancement

  • There's now more control over failing database connections.

• ACL enhancement

  • Previous functionality that allowed client items to be filtered via ACLs that directly reference a user, rather than a group, is now applicable to ACLs applied anywhere, not just the client.

• Edit grid panel filtering support

  • Non-spatial edit grids now support the same filtering as the non-editing grid versions.

• Updated feedback tools

  • The feedback tool now supports including the current map in the email.

• Index search update

  • The client controls for the index search now give better feedback when there is an issue with the search term.

• Index building update

  • The indexes now generate better results when the index is configured with a specific CRS.

• ArcGIS enhancements

  • There have been some improvements in the ArcGIS REST API map engine.

• WMS map engine authentication update

  • WMS map engines are better at handling services that require authentication and determining when a WMS service is unavailable.

• OSGi memd command update

  • The memd command now also includes style information associated with layers.

• Parameter updates

  • Where appropriate, parameters now support additional properties to set a minLength, maxLength, minValue, maxValue and increment.

  • A parameter can also support forceSelection and typeAhead (both boolean values) to turn on or off the type-ahead functionality for a list box and or force the first value to be selected.

• Request timeout update

  • Handling of requests that timeout on the server and handled in a more appropriate way in terms of the HTTP response code sent back to the client.

• JavaScript dependencies on the server are now all removed

  • Previously some functionality on the server was implemented in JavaScript, the last of that code has now been converted to Java.

• A new parameter added to BIRT reports

  • When a report is generated, a new report.entity parameter will be set to the name of the entity included in the report configuration (if it's included).

• Undo enhancement

  • The Selection Undo action is now more configurable, and now you can set zoom, active and turnon to true to enable the corresponding functionality.

• Filtering enhancement

  • Filters applied to spatial mappers are now applied more often so their functionality is available in a wider range of situations.

• Spatial edit update

  • There's a new guid() formula that can be used to populate a parameter with a unique id.

• Spatial upload enhancement

  • The spatial upload better handles styles that include text.

• EPSG code override

  • It's now possible to include an epsg.properties file in the workspace folder to add or override EPSG codes.

• NTLM authentication update

  • The server is now much better at catching NTLM header issues.

• Zip'n'ship update

  • The Zip'n'ship tool can now be configured to refine the list of entity that is it available for.

Fixes

• ToC action menu fix

  • When using the ToC button the first time the menu was displayed, it might not be in the best location.

• ToC panel fix

  • Some issues with styles have been resolved.

• Change to selection setting by external applications

  • When an external application updated a selection the corresponding layer was turned on by default, this has been reversed and now the external application must ask for the layer to be turned on.

• Interoperability fixes

  • Additional checks have been added to some functions that can be called by an external application to ensure that invalid parameters don't cause issues.

• Coordinate display issues

  • Displaying coordinates in DMS was sometimes incorrect.

• Lock and Style ToC menu fixes

  • These tool were failing when used against a tiled map engine.

• Redline fix

  • Completely transparent strokes weren't always working correctly.

• GeoJSON fix

  • Coordinates output as GeoJSON were rounding the coordinates when they should not have.

• Redline Arrow output update

  • The arrows generated on the server more closely match those displayed on the client.

• Grid filtering fixes

  • There have been some fixes in the way filtering of grid is handled when there are multiple wildcards in the filter.

• Spatial filter buffering fix

  • The spatial filter now checks if the buffer distance is zero before generating the buffer.

• Polygon parsing fix

  • Polygons sent from the client with holes in them, now that that's supported, are now also handled correctly on the server.

• FID mapping fix

  • Sometimes every hundredth FID in a list would not get mapped to the correct key.

• WMS server fixes

  • There have been a couple of fixes to ensure the WMS server handles the supplied parameters correctly.

2.5.27.6

Released 4 April 2019

Fixes

• Latitude/Longitude display issue

  • The latitude reported by the DMS conversion was not always correct

• Lock and Style ToC menu fix

  • The Lock Layer and Switch Style ToC context menu items caused problems with tiled map engines.

• minScale issue with tiled map engines

  • The map view minScale value was ignored if the map view has fixed scales set via a resolutions tag.

• Class breaks and Unique value renderer issue with ArcGIS

  • ArcGIS map services accessed via the REST API would fail if a class breaks or unique value renderer was used for a layer.

2.5.27.5

Released 22 March 2019

Fixes

• Spatial mapping filter fix

  • If a spatial mapper included a filter with user attributes the filter it would not always be applied.

• Spatial editing date fix

  • Spatial edits were always converting dates to GMT before writing them to the database.

2.5.27.4

Released 6 March 2019

Fixes

• Id mapping fix

  • In some circumstances, the mapping between entity id's and fid's would not include some id's.

2.5.27.3

Released 23 November 2018

Fixes

• WMS Map Engine

  • Enhancements to try and better detect failing WMS servers was too vigorous and may have determined that a WMS service was failing when it wasn't.

2.5.27.2

Released 10 October 2018

Fixes

• Installer JRE detection

  • If the embedded JRE wasn't selected during installation and an external JRE was chosen the installer would no proceed since it was looking for a JDK.

• ToC Action fix

  • The menu for the toc action would not always appear in the correct location.

2.5.27.1

Released 3 October 2018

Fixes

• BIRT Legend fix

  • The hide layers function of the BIRT legend component would not actually hide the listed layers.

2.5.27

Released 2 October 2018

Fixes

• BIRT Legend fix

  • The Legend component was not available in the BIRT report designer.

• Pink screen fix

  • The pink screen that appears on the client when a map engine is unavailable was supposed to be 50% transparent but it was fully opaque.

2.5.26

Not Released

Enhancements

• Index enhancement

  • An index search can now be set to turn on the layer associated (via the toc model) with the entity by setting doTurnOnLayer to true for the index combo in your client config.

• Spatial editing enhancement

  • You can now specify a table directly in the edit config that should be edited, rather than relying upon what's in the spatial mapping for the entity. This should help with editing entities that are spatially backed by a database view.

• Selection identify enhancements

  • Now allows you to tell it to just search visible layers, by setting useVisibleEntities to true in the tools config.

  • Now allows you to specify a buffer to use when selecting entities that intersect the selection, by setting bufferDistance, bufferUnits and bufferCrs in the tools config.

  • Now allows you to specify a spatial operation to use when selecting entities that "intersect" the selection, by setting spatialOperation to one of intersect, contains, overlaps.

  • Now allows you to specify if the active entity should be included in the search, by setting includeActive to true in the tools config.

• "spmd conf" command updated

  • The "spmd conf" command has been updated to generate better output.

• KML upload updated

  • The KML parser is now more forgiving of invalid KML files that are uploaded.

• KML label support

  • Uploaded KML files that include label points are now supported.

• Restart command update

  • The restart command gives better feedback if restarting is not available, rather than just saying that the command is not available.

• Reduce resource usage of NearMap panel

  • The NearMap panel will not try and retrieve map tiles when the panel is not visible.

• Reduce resource usage of Street View panel

  • The Street View panel will not try and retrieve map tiles when the panel is not visible.

• North Arrow in BIRT

  • BIRT includes a new North Arrow component that can be added to a report.

• Added ability to redirect the browser to a custom location if the user can't access a client

  • By setting the system property weave.noclient.redirect to a valid URL the user will be redirected to that page rather than get the default page displaying an error.

• Map tips updates

  • Map tips will now show the geometry of the related entity but this can be turned off by setting showGeometry to false in the map tip tools config.

  • A new visibleOnly flag has been added to the tool and individual map tips, to specify that the tips should only be displayed if the layer is turned on in the ToC. The default is false. There is also visibleOnlyMenu, which if set to true, adds a new menu item to the map tips menu to allow the user to turn the setting on or off.

  • Map tips can be grouped in the map tips menu by setting a group attribute for the tips. All tips with the same text for the group attribute will be included in the same sub-menu, and tips without a group attribute will appear in the main menu.

• checkAll and uncheckAll ToC panel context menu enhancements

  • These two items now allow you to set includeParent to true or false to change the behaviour of the tool with respect to also turning on or off any parent ToC entries (checkAll defaults to true and uncheckAll defaults to false).

• autoSelect added to list parameters

  • By setting autoSelect to false for a list type parameters you can stop Weave selecting the first entry in the list (when it's displayed).

• Automatically turn on a layer when an entity is selected

  • By setting turnOnActive to true in the ToC panel you can have Weave turn on the layer related to the active entity if it's not already visible.

• Update for URL redirect on the decline of licence acceptance

  • If Weave is embedded within another page/iframe you can set usetop to true in the client tip section and Weave will ensure that the whole page will be redirected to the URL specified as the link to go to if the user declines to accept the licence, rather than just the embedded page/iframe.

• Timeouts added to data definitions

  • Database related data definitions now have a server-side timeout, with a default of 120 seconds, to ensure that long-running queries do not hang around. You can set the timeout, in milliseconds, in the options for the data definition, or globally as a default, or turn it off completely.

• New entity labelling service

  • There's a new API available for providing user-friendly labels for entities, so if, for example, a user has to choose from a list of properties they can be shown a list containing the property address rather than the property id. Eventually, this will be used by client components in situations where picking an individual entity may be required (think mobile).

• New ToC API

  • A new ToC related API is available for map engines to implement so that they can provide structured ToC content, allowing Weave to directly use the groups defined in ArcGIS or a WMS map service for example when building a ToC model.

• Updated map API

  • There's a new method of accessing map API services, MapFactoryServiceProvider, that ensures that the service will be available when the caller requires it (rather than having the caller have to listen for the service before it can continue).

• ArcGIS Server map engine updates

  • Both the REST and SOAP ArcGIS map engines have had a number of updates to improve compatibility and performance.

• Map Engine Reset command added

  • It's now possible, via memd reset at the OSGi console or via the Admin UI, to tell Weave to clear any cached information it may have on a back-end map service (for cases when you change the service and need Weave to take note of the update).

• Health checks added to map engines

  • Health checks have been added for more map engine types.

• dbmd command update

  • The command has been updated so it handles table names in the format schema.table (as well as the older "table schema" style).

• spmd command update

  • The command has been updated so it outputs the count of records when describing a table

  • The command has been updated to produce a better output when using the conf option.

• New selection provider API

  • A new API is available to encapsulate the handling of selection so that more options are available for server components that utilise selection (for example allowing the selection to be provided by the client as part of a report generation request rather than requiring the selection to be sent to the server and saved before generating the report).

• Auto-focus for index combo can be disabled

  • The index combo gets the focus when the client starts, however it's now possible to disable this by setting autoFocus="false" in the index combo config.

Fixes

• KML label fix

  • Redlines exported as KML would not display any text associated with the redline (the text was exported as the item's description, not its name, which is what was required to have the text displayed in Google Earth for example).

• checkAll and uncheckAll ToC menu fix

  • The icons were missing for the new checkAll and uncheckAll ToC menu items that were added in 2.5.25.

• checkAll and uncheckAll ToC menu fix

  • The checkAll and uncheckAll context menu items were not being enabled when right clicking on a folder.

• Fix for using the non-default style on ToC model

  • If you specified a style for a layer entry that wasn't the default, the ToC menu would display that as chosen style but the map would not reflect the changed style.

• Fix for polygons with holes

  • In some circumstances, polygons that contained holes did not include the holes when the polygons were sent from the client to the server.

• Fixed up some highlighting issues

  • There were some issues with overriding the geometry highlighting styles that have been resolved.

• Fixed some filename encoding issues

  • Uploaded files would sometimes not be downloadable if the filename contained some special characters.

• Improved time handling in non-spatial editing

  • Time columns are now handled better when used with non-spatial editing.

• WMS map engine fixes

  • Some minor style related fixes have been added to the WMS map engine (when working with QGis).

• Weave security fix

  • The IPFilteredSpnegoAuthenticationProcessingFilter filter wasn't actually applying the IP filtering when used in security.xml.

• Fixed issue with DXF export

  • If you generate a DXF file it was producing polylines when it was supposed to produce polygons.

• Map tips won't turn off

  • If you set pressed to true for the map tips tool then the user couldn't turn the tool off.

• Redline export tools enabled when they shouldn't be

  • The Export to Shapefile and Export to KML buttons were enabled when there were no redline items.

2.5.25

Released 4 June 2018

Enhancements

• Health checks for ArcGIS

  • The ArcGIS map engine now supports health checks allowing you to monitor the health of ArcGIS map engines used by Weave.

• Index limit changed

  • The default number of items returned for an index search, if the client doesn't request a specific number, has been updated from 10 to 500. This allows you to set a pageSize of 0, which turns off the paging of the index results, and get more than 10 results back. A new system property, weave.index.limit, can be used to change this limit, and/or set it back to 10 if there are problems. Note that the default Weave client requests 10 items, so this change should not affect any of those, it's only custom clients and those who want to remove the paging by setting pageSize to 0.

• CRS for Circle operations

  • Tools that use a circle for their operation now support specifying a CRS for the tool to use. Setting a crs value for the configuration of such a tool in the client, will force the tool to use that CRS when displaying values.

• Anonymous user local storage

  • Stored items, e.g. redlines, bookmarks, are now stored in the browser for anonymous users, allowing them to save those items across a browser restart (in supported browsers, i.e. those that support JavaScripts localStorage API).

• New ToC menu items

  • The weave.toc.checkAll and weave.toc.uncheckAll items can be added to the ToC context menu to turn on/off all items in a group.

• Improved CRS handling with spatial editing

  • Submitting a spatial edit has improved support for submitting geometry that's in a different projection to that of the underlying data.

• Data generation API enhancement

  • When generating data from some geometry it's now possible to specify the type of spatial operation to use beyond just overlaps. The caller can now specify if the spatial operation should be one of overlaps, intersects, contains, within or closest.

• BIRT designer update

  • The test connection button in the BIRT report designer will now actually test the connection.

• Improved parsing of metadata and primary key information in spatial engines

  • The parsing of the metadata and primary key information embedded in a spatial engine config will now trim extra spaces in the names.

• ACL enhancement

  • It's now possible to enable an ACL entry to target a specific user rather than just a role. Note that this has to be enabled by setting the system property weave.enable.user.acl to true.

• Zip'n'ship menu enhancement

  • When exporting spatial data it's now possible to set a crs value in the zip'n'ship menu to override the CRS used in the client.

• SQL Server geometry enhancement

  • A wider range of geometry types exposed by SQL Server is now supported, e.g. circular strings, curves and surfaces.

• Selection legend enhancement

  • The generation of the legend symbology for items where we don't know the underlying geometry type has been improved.

• Spatial upload enhancement

  • A layer uploaded via the spatial upload tool now supports the context menu "zoom to layer" item.

Fixes

• Anonymous storage fix

  • Stored items for anonymous users was being saved on the server when it shouldn't be.

• High CPU usage fix

  • A problem that could result in high CPU usage for extended periods has been resolved.

• 'editor health' command fix

  • The health command for the editing bundle was reporting the health of everything, not just edit related items.

• CRS override fix

  • In some circumstances, a CRS override set in a spatial mapper was not being taken into account.

• Grouped edit parameter labelling issue

  • Edit parameter in a group was not showing the correct group label.

• Grouped edit parameter issue

  • Grouped edit parameters were working incorrectly.

• Session issue fixed

  • A handling of the situation when a HTTP session could not be created has been improved.

• Buffer operation fix

  • Some buffer generation operations weren't checking for 0 distance buffers and handling the situation correctly.

• Empty legend fix

  • The text set to display when there were no items to be displayed in a legend was not being used.

• ArcSDE feature cache issue

  • The thread used to manage the ArcSDE feature type cache could stop the server from shutting down in some circumstances.

• BIRT legend hide fix

  • A flaw in the boolean logic of when to hide legend layers was fixed.

• ArcGIS map engine legend fix

  • The ArcGIS legend generator was not honoring scale dependencies correctly.

• Bookmark loading issue

  • Fixed an issue where new folders added to a ToC model after a bookmark was saved (which includes Uploaded data) wouldn't be turned on when a bookmark was loaded.

• Admin UI fix

  • Renaming a file via the Admin UI wouldn't always work.

• Admin UI fix

  • Cutting and Pasting wasn't working for directories.

• Kerberos security update

  • Fixed a couple of small issues with Kerberos authentication.

2.5.24.6

Released 31 May 2018

Fixes

• Anonymous user storage issue

  • Information for anonymous users that should not have been saved on the server, redlines, bookmarks, etc, was being saved on the server, resulting in all anonymous users sharing this information.

  • This fix has also been made available for 2.5.21, 2.5.22 and 2.5.23.

2.5.24.5

Released 31 May 2018

Fixes

• CPU usage fix

  • An issue was discovered that could cause the CPU usage to spike to 100% and require a restart.

  • This fix has also been made available for 2.5.21, 2.5.22 and 2.5.23.

2.5.24.4

Released 4 April 2018

Fixes

• Spatial data fix

  • Generating data based on spatial operation could sometimes cause an invalid filter to be used.

• ArcGIS REST tiled map engine fix

  • The extents for REST based tiled map engines wan't being calculated correctly resulting in them being clipped on the client.

2.5.24.3

Released 13 March 2018

Fixes

• ArcGIS SOAP map engine fix

  • There was an issue with layers that had numeric names that was fixed.

• Core map engine fix

  • The internal cache of generated map images wasn't always cleaning out old images.

• Spatial operation fix

  • Generating data based on spatial operations for selected entities would fail for points in some circumstances.

2.5.24.2

Released 20 February 2018

Fixes

• BIRT legend component fix

  • Due to a reversed logic condition in the code the showing/hiding of layers in a legend didn't always work as intended.

2.5.24.1

Released 15 February 2018

Fixes

• BIRT map component fix

  • An enhancement in 2.5.24 that allowed you to use a formula to specify layers to show or hide cause the regular processing of a list of layers to stop working.

• Weave map engine fix

  • If a style was missing for a layer in the Weave map engine it would stop the engine from working at all.

2.5.24

Released 8 February 2018

Enhancements

• ArcGIS REST Map Engine legend update

  • The ArcGIS REST Map Engine now supports aliases when displaying the legend in a BIRT report

• ArcGIS REST Map Engine update

  • You can now specify a referer property in the map engine config have that value sent as a referer header to ArcGIS when making requests from the Weave server

• Support dump update

  • A support dump now includes the style.css file is one exists

• Optimization of spatial filter

  • Some spatial filters generated inefficient SQL clauses when filtering on a list of values, in certain cases this has be changed to use an IN clause which should be quicker

• Optimization of user attribute spatial filters

  • A filter applied to a spatial mapping that used user attributes would generate inefficient SQL when there were lots of values for the user attribute, this has been changed to use an IN clause

• Grid panel update

  • Now if a column is hidden in a grid panel the column will not be included in the data is exported to a different format

• Cascading form parameter enhancement

  • Cascade parameters now support adding a label and having the fields grouped within that label

• Removed obsolete warning

  • A warning about REST map engines has been removed because it's no longer applicable and was causing confusion

• Layer access logging enhancement

  • Individual layer accesses are recorded to log layer access counts

• Handling of groups in ArcGIS updated

  • You can now specify if Weave honors or ignores groups from ArcGIS. Setting ignoregroups to false (true is the default) for a AGS map engine will instruct Weave to include a layer entry for the group when it loads the information from ArcGIS, allowing you to turn on and off groups directly. If you're having issues with AGS map toc models not doing the right thing, try changing this value for the map engine.

• Selection transfer API update

  • The selection transfer config no longer requires a userid column in the table it works with

• BIRT report CRS update

  • It's now possible to set the CRS that a map component should use directly in a BIRT report UI. Previously this had to be added manually.

• New spatial validation API

  • A new API to check spatial object has been added, this will be used down the track to check config entries to ensure that tables, columns, etc that are referenced in a config file are valid when the config is processed, rather than waiting until the items is used.

• Improved formatting of numeric values

  • Some database columns were including additional trailing zeros when displayed in a grid panel, this update should tidy up these values

• Improved internal search API

  • The API used to perform a search has been enhanced to support additional ways to provide the values for a multi-valued input field

• Updater enhancement

  • When running the updater on a Weave instance that uses Subversion for revision control, the updater will add and remove changed files for you

• Kerberos authentication enhancement

  • There's now the ability to remove the realm from user names when a user is authenticated via a Kerberos server

• REST API update

  • The REST API is more relaxed about the JSON it accepts, no longer requiring attribute names to be quoted

• Security code update

  • Some old security related code has been removed to tidy up the security handling

• Security handler update

  • Security handler now have more control over the information they expose to the rest of the system, making it easier to customize the user experience based on the underlying security provider

• WMS server update

  • The Weave WMS server now handles non-integral DPI values

• Third party module update

  • There are now proper .msi installers for any Weave integration components that need to be installed on client PC's

• Excel export enhancement

  • URL's in Excel files are now clickable links

• Security update

  • A major update to the security code to tidy up and enhance the supported security options (Kerberos, JWT, OAuth)

• BIRT layer update

  • It's now possible to specify the layers to show/hide in a BIRT map component using a formula (which can be set using a report parameter, for example)

Fixes

• Index fix

  • Indexes couldn't be updated unless they already existed

• Data generation fix

  • If a client requests a sub-set of available columns for a data definition the metadata returned to the client included all columns, not just the sub-set that was asked for

• Grid panel API fix

  • Hiding a column in a grid panel was not firing an event to let other components know that the column has been hidden

• minScale issue with tiled ArcGIS map engine

  • The minScale value in a client was not being used if the available scales were being set using a resolutions value (rather than a scales value)

• Non-spatial editing fix

  • BLOB and CLOB type columns were not being handled well

• History tables in non-spatial editing fix

  • The geometry column would trip up history table handling when non-spatial editing was done on a spatial table

• Spatial identity fix

  • When the spatial identify tool was configured to only display results for visible layers it wouldn't work for those layers in a group

• Map API initialization fix

  • The map panel was setting its internal "ready" flag after firing a ready event, it should be set before

• KML export issue

  • The KML export in the Zip'n'Ship tool wasn't closing the KML file after generating it

• Temporary directory handling fix

  • The support code for working with temporary directories would sometimes run into issues and couldn't create new temporary directories

• Zip'n'Ship failing

  • The Zip'n'Ship tool would sometime run into issues if it could create a temporary directory

• Filtering in client toc panel

  • Filtering the ToC panel would show layers it shouldn't when the layers were in groups that were non-expandable

• Selection identify fix

  • The selection identify tool would fail completely if there was an issue with a single layer (rather than returning info for the layers it can access)

• Redline text fix

  • The redline text tool was drawing the text placement point when rendering the redline items on the server

• Security startup update

  • Some of the security related bundles had to be started in a particular order or they wouldn't work, this is not longer the case

• REST API fix

  • The REST API was exposing some internal classes that it shouldn't have been

• Spatial edit fix

  • Some spatial edits were not closing their connections to the database

• Edit input panel fix

  • The input panel would not always reset after successfully submitting an edit

• weave.war update

  • The weave.war file was updated to improve the guessing of what servlet API version is actually available

2.5.23.1

Released 24 October 2017

Fixes

• Index build issue

  • An index could not be built unless it already existed

2.5.23

Released 18 October 2017

Enhancements

• i18n support for legend labels

  • Legend labels now support i18n

• Support for custom stylesheets

  • Creating a CSS file called styles.css in the workspace would include the content in the client, allowing for simple overriding of CSS styles

• Buffer style enhancement

  • The buffer style can be set in the map view

• ToC filtering enhancement

  • Clearing a toc filter will restore the ToC expanded/collapsed state to the state it was before the filtering

• Update lat/long display

  • Changed the seconds display to include the fractions of a second

• Data display enhancement

  • Added support for setting numeric, date, time and timestamp formatting patterns in a grid panel

• Added support for field groups

  • Client input forms, built via <parameter> config items, can now group fields

• Map highlight enhancement

  • It's now possible to specify that highlights and buffers are automatically removed from the map after a fixed delay, rather than waiting until the new map redraw.

• Report panel enhancement

  • Groups expand and collapse based on the active entity

• Search panel enhancement

  • It's possible to change the default icon for the search panel

• Data enhancement

  • A join in a data definition now supports sub-clauses (with user attribute substitution)

• Non-spatial edit enhancement

  • Lists in non-spatial edit input forms now support i18n

• Email feedback form update

  • The email feedback form has better i18n support and more configuration checking

• ArcGIS map engine image server support

  • The ArcGIS REST API can now be used with Image and Map services

• WMS enhancement

  • The client scale can be included in WMS GetMap requests, to improve the scale dependent rendering done by the WMS server

• Parameter group update

  • Parameter groups can now be created with a single sub-parameter, previously they required at least two parameters

• Parameter ACL update

  • Parameters support acl's

• Report API update

  • Some new functionality has been added to the internal report API

• Report update

  • Reports now expose "published", "group", "iconCls" and "enablesFor" attributes

• Improved BIRT legends

  • Legends are a bit neater in BIRT reports

• Improved BIRT maps

  • Handing of map scale formulas errors is more robust

• Buffer enhancement

  • Various buffer related tools can now be configured to specify buffer generation parameters (include CRS to generate buffer in)

• JCIFS update

  • Updated the JCIFS third party library

• Improved overriding settings

  • Variables in config files can be set within the config file using <?set name=value>, for the JVM using -Dname=value, or from the environment using SET name=value. The order that they are read from has been changed to help when starting Weave in a container. The order is now environment, jvm and then config, this makes it easier to set defaults but have the overwritten when the server starts.

• Updated entity geometry and centroid code

  • The code now always returns the CRS of the generated geometry

• Support dump enhancement

  • Removed some content that was random and not important from some output to make it easier to compare different support dumps

• Spatial edit enhancement

  • The createNew action will turn on the layer associated with the entity (if one is set)

• JSON API update

  • Updated JSONIterator API to better handle null source objects

• Assetic integration update

  • Assetic window is now resizable

• Data API update

  • Added support for data generation based on entity intersection (and buffer)

• Entity API update

  • Added internal Entity class so as to not expose the internal Entity class

• Geometry API update

  • Added additional filtering options to geometry API when fetching layer geometry

• Map API update

  • Improved streaming support in the map API

Fixes

• JavaScript minimisation fix

  • Fixed an issue where a regular expression at the end of a line of JavaScript would cause minimisation to generate incorrect code

• Redline fix

  • Loading a redline would not offer a warning that the contents were about to be replaced if it was configured to do so

• Transparency slider fix

  • The new transparency slider wouldn't work when used with a non-expandable group

• A couple of small fixes for the Google panels

  • Checking if the StreetView panel has started correctly and stopped limiting of new Google layers types

• MapTip date/time fixes

  • Handling of dates and times in map tips has been fixed

• Measure polyline fix

  • If minKm was used the conversion wasn't always done correctly in the measure polyline tool

• Grid highlight fix

  • Setting an xand ycoordinate in a data definition to have the grid row highlight a different point on the map when a row was clicked wouldn't work unless a crswas also included. See Client Views Datafor more info.

• ToC filter fix

  • Setting collapseOnClear to false would cause ToC entries that should be hidden to be shown after the ToC filter was cleared

• SwitchView action fix

  • The SwitchView action only worked on tab and card layouts, now it should work on accordion layouts also

• ToC load fix

  • Fixed an issue with exclusive groups when loading a ToC model (from a bookmark for example)

• Entity combo fix

  • Fixed issue when entity combo had been narrowed down to set of entities but the default entity wasn't one of them

• URL link fix

  • Sometimes clicking on a link would display a warning about not being able to open the link while it did actually open the link (if this still happens set openWithScript to true)

• Radio button fix

  • Some forms wouldn't package up radio button values correctly when sending them to the server

• GeoJSON encoding fix

  • Generated GeoJSON wasn't including the "properties" attribute if there weren't any properties, but according to the spec it should always be included

• JSON encoding fix

  • The logic for encoding objects into JSON has changed slightly to produce more consistent results

• Non-spatial editing fix

  • Invalid input forms were still allowed to be submitted

• Non-spatial editing fix

  • Fixed handling of text fields with "MAX" size.

• Index building fix

  • Sometimes after building an index it wasn't replacing the index content with the newly generated content

• Legend genarator fix

  • Legend images for layers with multiple geometry type is handled better

• ArcGIS REST API fixes

  • Various fixes for working with ArcGIS REST map engines

• ArcGIS SOAP API fixes

  • Some improvements when working with projections on ArcGIS SOAP map engines

• Fixed BIRT maps

  • The reported scale would be wrong if the DPI was not the default for a map component

• Fixed BIRT scale rounding issue

  • Fixed some rounding issues resulting in scales like 2500.00000000000001

• Spatial edit fix

  • Fixed an issue when the filter that was generated to select the record to update

• Spatial edit fix

  • Dates are now stored using GMT

• Spatial edit fix

  • Tidied up handling of default values when submitting an update

• Search API fix

  • The search API was using the target entity instead of the source entity when performing an entity intersection search

• Zip'n'ship fix

  • Fixed issue when exporting records with more than one geometry column

• Zip'n'ship MIF fix

  • Fixed issue generating MIF file with mixed geometry

• IE POST fix

  • Fix for zero length POST issue is also applied to PUT requests

• Fixed "Jersey not ready" error

  • This issue would sometimes stop the server from starting up properly removing access to a number of functions including the admin UI

• ToC expand/collapse fix

  • Expanding a ToC model, using the expand button, would result in non-expandable groups being expanded

• OpenLayers scale rounding issue

  • When OpenLayers calculates scales based on a list of provided resolutions JavaScript rounding issues would sometimes result in scales like 2500.00000000000001 which would cause issues elsewhere

2.5.22.6

Released 9 October 2017

Fixes

• Fixed an issue with a popup message warning that a link could not be opened when the link was in fact opened

  • The JavaScript used to open a link and determine if it was opened can not be relied upon 100% of the time when using Internet Explorer, so sometimes, depending on Protected Mode and other security settings, the browser may indicate that a link did not open and the user has to click the link manually but they can disable their popup blocker to not see the message, but the link did in fact open. If you see this you can set the openWithScript option to true, since the JavaScript clearly did open the link this will make this the default way to open links in future. Setting openWithScript to false will force the popup window to always appear, and not setting it at all will attempt to use JavaScript, but if that fails then use the popup window.

2.5.22.5

Released 15 September 2017

Fixes

• A couple of small fixes for the Google panels

  • Checking if the StreetView panel has started correctly and stopped limiting of new Google layers types.

• Editing fixes

  • Fixed issue with filter used to search for the record to update.

  • Fixed issue with dates and times being created with incorrect timezone.

  • Fixed handling of text fields with "MAX" size.

• Zip'n'ship fixes

  • Fixed issue generating MIF file with mixed geometry.

  • Fixed issue when exporting records with more than one geometry column.

2.5.22.4

Released 13 September 2017

Fixes

• Fixed "Jersey not ready" error

  • This issue would sometimes stop the server from starting up properly removing access to a number of functions including the admin UI.

2.5.22.3

Released 6 September 2017

Fixes

• A handful of small client fixes

  • Including fixes for polyline measure, spatial identify, toc, entity combo and check-boxes.

• Fix for legend generation

  • Legend images for layers with multiple geometry type is handled better.

• Report scale fix

  • Map scales in reports are handled better.

2.5.22.2

Released 18 July 2017

Fixes

• Transparency slider in ToC context menu

  • The new transparency slider wouldn't work when used with a non-expandable group.

• Index building

  • Sometimes index building wouldn't be able to update the index and the index would be lost.

• Date handling when editing

  • The spatial edit would sometimes mess up the time zone for date fields.

• Stack overflow issue

  • An issue when packing up map engine information and sending it to the client has been fixed.

2.5.22.1

Released 6 July 2017

Fixes

• Grid highlight fix

  • Setting an x and y coordinate in a data definition to have the grid row highlight a different point on the map when a row was clicked wouldn't work unless a crs was also included. See Client Views Data for more info.

2.5.22

Released 26 June 2017

Enhancements

• DMS update

  • The buttons for the document management system will now disable themselves if there are no documents associated with the current selection.

  • This has to be enabled by setting monitor to true for the DMS actions in the client config.

• Interop update

  • The way Weave can be launched from other application has been improved. It no longer requires WeaveLink to be installed (but having it installed will improve the functionality).

• Buffer tools update

  • Tools related to buffering can now specify a crs attribute to force the buffer calculations to be performed in the specified coordinate reference system rather than that of the underlying map.

  • This is useful if you're using a geographic or display oriented projection on the client but wish to perform the calculations using a local projection to make the calculations more accurate.

• Small mapping update for blank maps

  • The client will now use a local "blank" image when there's nothing to draw for a map layer rather than fetching the image from the server each time.

• Removed Google Earth plugin support

  • The Google Earth plugin is no longer supported by Google and no longer works so it has been removed.

• Spatial identify tool update

  • The spatial identify drill-down tool can now change the setting for the size of the entity list.

  • entityListWidth, entityListWidthMin and/or entityListWidthMax can be set for the weave.spatialIdentify(or com.cohga.html.client.map.spatialIdentify) tool (default/current values are 220, 175 and 400 respectively).

  • useVisibleEntities will filter the entity list based on the ToC state. See Client Actions Spatial Identify.

• Improvements to toc filtering

  • The toc model will be collapsed if the filter is cleared (setting collapseOnClear to false will disable this).

  • The filter regular expression will be escaped to better support special characters that may have been interpreted by the regular expressions (setting escapeFilter to false will disable this).

• Entity selector update

  • The entity selector combo and panels will always include the default entity if the entity list has been filtered but the default entity was not included in the filter list.

• Download link update

  • The intermediate window that appears if you try and open a link has been updated to better indicate that it is appearing because popups are being blocked by the browser.

• Acetate update

  • The Acetate rendering API and implementation have been updated to support non-integral DPI values.

• Update to data generation API

  • The low-level server API for generating data has been expanded, it now provides new interfaces for counting and generating data in one operation.

• Update to handling of "joined" tables when generating data

  • When you specify a join table in a data definition, for use when you have complex sorting or grouping for example, the population of the join table was happening twice, once when the count of the total number of available rows was calculated, and again when the actual data was retrieved. This has now been changed so that it only occurs once.

• Document response update

  • When sending a JSON response to the client for an intermediate document link the content type of the response wasn't being set and would cause IE to complain about the lack of a content type.

• Updated mapping API

  • A new mapping API has been added to provide additional advanced mapping capabilities (rotation, re-projections, non-integral dpi, etc).

• Tiled map engine update

  • Tiled map engines can be re-projected on the server. This is useful when generating a map in a report in a different projection than the client.

• Weave map engine update

  • The Weave map engine handles CRS errors better.

• Third-party library update

  • Some of the third party libraries that Weave relies upon, related to REST API's, have been updated.

• Image handling updates

  • Improved support for generating JPEG and TIFF images.

• Editing updates

  • The user is not able to change the active entity when performing an edit.

  • Additional validation checks are performed on geometry before being submitted.

• GeoTools updates

  • Some GeoTools related bundles have been updated to the latest supported releases.

Fixes

• Interop fix

  • A message was being output to the browser console indicating that the WeaveLink component may be out of date when it wasn't.

• Legend action fix

  • The legend action, not the legend panel, was not honouring the remove attribute.

• Colour selection fix

  • The colour palettes for selecting redline or upload colours would cause problems if the palette was initialised with a colour that wasn't available in the palette. This could happen for example if an item was programatically added to the redline, rather than the user drawing the item manually.

• Measure tool save to redline fix

  • The measure distance we appearing in the redline multi-line label field when the redline measure items wasn't selected.

• Bookmark fixes

  • Restoring a ToC from a bookmark saved by Weave 2.4 could cause problems.

  • Restoring a ToC with an exclusive group would turn on the parent even if it was off in the bookmark.

• Error message fix for search panel

  • A bug in Ext.js meant that error flags were not being removed from the search panel when the error situation was resolved.

• Data generation fix

  • An error could occur when generating data based on an entity intersection when there were no available entities, which should be returning no data rather than generating an error.

• ArcGIS Server WMS fix

  • Scale dependencies were not correctly set when using ArcGIS server via WMS.

• BIRT scalebar component update

  • Scale values were not correct if using a DPI other than 96 and the map was setup to use the client view extent.

• BIRT map component update

  • Setting a crs attribute for the map would not force the map to use that coordinate reference system.

• Multi-select parameter fix for searches

  • Search parameters that allowed for more than one value to be selected were not always generating the correct SQL.

• Date parameter issue in search panel

  •  

    • Validation of date fields was causing problems if the validation failed.

• Fix for spatial mappers that had multiple spatial engines

  • The update in 2.5.21 that validated table and key information caused some types of configurations to stop working, this update allows those configuration to be used again.

• Measure tool save to redline fix

  • The items saved to the redline layer were not being drawn on the map when the server would generate a map image, e.g. when generating a report.

• OGR spatial engine fix

  • The OGR based spatial engines were returning some field types as the incorrect type.

• ArcGIS tile offset

  • The need to specify a tile offset for tiled ArcGIS map engines has been fixed and tiles should now align correctly without the offsets (which will now be ignored)  

2.5.21.9

Released 29 May 2017

Fixes

• BIRT scalebar component update

  • Scale values were not correct if using a DPI other than 96 and the map was setup to use the client view extent.

2.5.21.8

Released 26 May 2017

Fixes

• BIRT map component update

  • Setting a crs attribute for the map would not force the map to use that coordinate reference system.

2.5.21.7

Released 23 May 2017

Fixes

• Multi-select parameter fix for searches

  • Search parameters that allowed for more than one value to be selected were not always generating the correct SQL.

2.5.21.6

Released 3 May 2017

Fixes

• OGR spatial engine fix

  • The OGR based spatial engines were returning some field types as the incorrect type.

2.5.21.5

Released 11 April 2017

Fixes

• Data generation fix

  • An error could occur when generating data based on an entity intersection when there were no available entities, which should be returning no data rather than generating an error.

2.5.21.4

Released 11 April 2017

Fixes

• Legend action fix

  • The legend action, not the legend panel, was not honouring the remove attribute.

2.5.21.3

Released 3 April 2017

Fixes

• Bookmark fixes

  • Restoring a ToC from a bookmark saved by Weave 2.4 could cause problems

  • Restoring a ToC with an exclusive group would turn on the parent even if it was off in the bookmark

• Colour selection fix

  • The colour palettes for selecting redline or upload colours would cause problems if the palette was initialised with a colour that wasn't available in the palette. This could happen for example if an item was programatically added to the redline, rather than the user drawing the item manually.

• Measure tool save to redline fix

  • The measure distance we appearing in the redline multi-line label field when the redline measure items wasn't selected.

2.5.21.2

Released 28 March 2017

Fixes

• Measure tool save to redline fix

  • The items saved to the redline layer were not being drawn on the map when the server would generate a map image, e.g. when generating a report.

• Date parameter issue in search panel

  • Validation of date fields was causing problems if the validation failed.

2.5.21.1

Released 25 February 2017

Fixes

• Fix for spatial mappers that had multiple spatial engines

  • The update in 2.5.21 that validated table and key information caused some types of configurations to stop working, this update allows those configuration to be used again.

• WMS map engine fix

  • A fix for scale dependencies when accessing ArcGIS server map services via WMS has been applied.

2.5.21

Released 21 February 2017

Enhancements

• Redline shapefile export enhancement

  • Ability to define projection tags within a single projections tag when setting available projections for the redline shapefile export.

• Bookmark menu

  • The published bookmarks are now sorted by the user and label.

• Caching of page templates

  • Generation of the HTML page templates is cached so they do not have to be re-compiled on each client access.

• Measure tools

  • Number of digits displayed can be changed by setting digits value, default is 3.

  • New button is added to the measure window allowing the previous measure geometry to be added to the redline layer.

  • Initial window placement has been changed to not be in the middle of the screen.

• Entity selector

  • Improvements in the entity selector drop down list to help with filtering the listed entitites.

• List box filtering

  • It's now possible to change the type of filtering used for some list boxes so that they don't just filter based on a match at the start of the text, by setting matchType to middle or end you can filter where the text is in the middle or at the end of the label, the default is start.

• GeoJSON API improvement

  • The server GeoJSON support has been improved.

• JDBC driver enhancement

  • It's now possible to force a JDBC connection to use the native test to see if a connection is valid, by setting the system property weave.jdbc.useisvalid to true.

  • It's now possible to specify the maximum age for a pooled JDBC connection, by adding maxAgeMillis to the connection properties.

  • It's now possible to specify if pooled JDBC connections are used in a lifo or fifo order, by setting lifo to true in the connection properties (default is to use first-in, first-out).

• i18n improvement for grid export

  • Headers in the export can now be localised as well as the content.

• Index results style enhancement

  • Additional CSS styles have been added to the index combo box to allow improved customisation of the display.

• ArcGIS Server

  • Additional monitoring of ArcGIS Server requests has been added.

  • Grouped layers are handled better when turning on/off visibility.

  • The AGS SOAP library has been updated.

• WMS map engine

  • You can now set swapAxis to true for a WMS map engine to force it to send coordinates ordered as y,x, for use when working with a WMS 1.3 map engine that uses a CRS that orders the coordinates as y,x rather than x,y.

• Updated internal ApacheMQ library

  • A library used internally, for things like vehical tracking, has been updated to a later release.

• Ongoing removal of server side JavaScript

  • Some server side code makes use of JavaScript to perform its initial processing of client requests, this is being removed and replaced with native Java code.

• Ability to specify support report formats per report

  • You can now set a format value in a BIRT report config to refine what formats are available for a report, e.g. <birt:report id="example" format="html,pdf" label="Example" .../>

• Caching headers for WMS server

  • The Weave WMS server now includes browser cache headers in the responses to help client performance.

• Spatial editing

  • A new weave.edit.createNew button is available for directly starting the creation of a new object, e.g. it switches to the correct entity and starts a new edit.

• Swagger update

  • The Swagger information can be customised (Swagger is the REST API documentation tool used by Weave).

• Postgres

  • The Postgres JDBC driver has been updated.

• Redline toolbar update

  • It's now possible to configure which tools and settings menus appear in the redline toolbar by adding geometryTool and/or settingTool values to the redline action.

Changing what appears in the redline toolbar

•  

  • The default tools that are available are point, polyline, polygon, circle, square, rectangle, marker and text

  • The default settings that are available are fill, stroke, font, markerMenu

• Measure tools update

  • Updated measure tools to allow hiding of individual measurements.

Hiding measurements

•  

  • Obviously you would not want to hide all of them, they're just listed above for completeness, also you may want to adjust the window hight by setting a windowHeight property, which defaults to 100 but would be smaller if you remove an item or two.

• Bookmark update

  • The map CRS is not stored with the bookmark extent so that the bookmark will still work when used with a different client that has a different CRS.

• New layer transparency tool

  • There a new action available for the ToC context menu, weave.toc.layerTransparency, that allows you to add a menu entry to adjust the opacity of the map engine the layer belongs to.

• ToC panel enhancement

  • a new checkParentOnVisible flag has been added to the ToC panel that when set to true will ensure that parent check-boxes are checked when a child check box is turned on.

• Spatial mapper enhancement

  • Spatial mappers will now check the table and key values when the spatial mapper is created, rather than waiting until it is used.

  •  

     

    This element has conversion issues

    Learn More

     

     

Fixes

• Redline arrow head fix

  • The menu option for selecting the type of arrow heads for a line was not being disabled when the stroke style was set to "none".

• Redline i18n resources

  • Some text for the redline export were not setup to be able to be set using i18n resources.

• Geometry rendering bug

  • Fixed an issue with drawing of geometry in the client when you zoom in to close to the geometry.

• Zoom to layer min/max scale issue

  • If you were using fixed map scales then the zoom to max/min actions on a ToC layer may not display the layer because it'd zoom to the closest scale, rather than the scale that would ensure the layer was visible.

• TerraMap fix

  • There was a browser issue that caused the TerraMap panel to be to short.

• Editing date handling

  • A minor fix was added to fix a problem with date handling in the non-spatial editing.

• Indexing fix for non-text characters

  • The indexing has been tweaked to better handle non-text characters at the end of the search query.

• Fix for selection SQL

  • The SQL/CQL generated to filter selection has been changed to be more reliable.

• Zip'n'ship startup issue

  • Sometimes Weave would try and start zip'n'ship bundles when they were already starting.

• StreetView fix

  • An overlay for the StreetView panel that shows the overview would stop interaction with the view from working.

2.5.20

Released 12 Septenber 2016

Enhancements

• Arrow support in redline

  • You can now set arrow heads on lines added to the redline layer.

• Ajax API update

  • The internal Ajax API now allows the Requested-By header to be turned off by the caller (after it was found that some web API's don't like the header).

• Null/Not Null support added to Ad-Hoc query

  • The Ad-Hoc query builder how has a null/not null option.

• Spatial identify change

  • The spatial identify tool now clears the window content earlier in the process to make it clearer as to what the grid content refers to.

• Added support for UUID key columns

  • Data definitions can now use a column that is a UUID type as the key.

• New internal Entity API

  • The client and server API's for dealing with entities have been tidied up to make them cleaner for multiple uses.

• New map description API

  • The map description factory now exposes an API that allows the map scale to be directly set.

• ArcGIS Map Engine update

  • The ArcGIS map engine now uses common coordinate system reference code in preference to ESRI specific ones.

• Support for wildcards in layer filters

  • You can remove and limit layer a map engine exposes using * as a wildcard in the layer id.

• Weave map engine update

  • Improved the style handling of the Weave map engine, including better support for mixed geometry type layers.

• Additional logging on error

  • When a client request causes an error additional information is recorded in the weave.log to try and help resolve the cause.

• Status page updates

  • Some of the information in the status page has been tided up.

• New action for spatial editing

  • There's a new action that allows you to directly create a new entity (rather than having to switch the active entity, choose the edit to apply then use the create button).

• TAB and MID/MIF support for spatial upload

  • MapInfo files can now be uploaded.

• TAB support for zip 'n' ship

  • MapInfo TAB files (MID/MIF was already there) can now be downloaded.

• Updated zip 'n' ship selection tool

  • The tool to extract just the current selection has been updated to allow more control over the extraction.

• Admin UI enhancements

  • A number of additions have been made to the Admin UI including tools to:

    • Build and test indexes

    • Check the health of your Weave system

    • Report on Server Status information

    • Allow configuration file editing

Fixes

• Search config fix

  • If a label has not been set for a search it will no longer stop the search from being available.

• Other small fixes

  • A number of other minor issues have been resolved.

2.5.19

Released 12 July 2016

Enhancements

• Map generation update

  • The code on the server side that generates map images has removed dependencies on JavaScript to make it more robust.

• Database document storage update

  • The Database provider for the document storage API now supports a configuration where you can set separate read and write database connections.

• Sortable list parameter changes

  • Previously list parameters were sorted by the label, which wasn't always suitable, so recently the sorting was removed entirely and left up to the underlying data definition, but that required too many sites to have to change their configuration to get the old ordering back, so the default for list sorting has been set back sorting by label. Now you can specify a different sort order for a list parameter by setting a sortAttribute value for each list parameter. The attribute accepts the following values: label, value, none, defined or default, or it can be set to the same value as either the labelColumn attribute or the valueColumn attribute. label will sort by the label column, value will sort by the value column, none will perform no sorting at all (useful for inline data definitions), defined will leave the sorting up to the underlying data definition (this assumes that the data definition has one or more sort tags, or it would be the same as setting to none), finally, default, which is the same as not setting a value at all, use the default sort (which at the moment is sorting based on the label column).

• Log output reduction

  • Some log output that was being recorded at INFO level has been reduced to DEBUG level to remove unnecessary output when you want to minimise log generation.

• User attribute support for report parameters

  • BIRT reports now support the passing of user attributes as report parameters, allowing BIRT reports to be customised based on attributes associated with the user.

Fixes

• OSM tiled map engine fix

  • There was a concurrency issue with the OSM tiled map engine when it came to determining which URL to access.

• Spatial data generation fix

  • Spatial data connections had an issue if the key attribute was also used in a parameter.

• WMS layer filtering fix

  • A minor issue related to filtering available layers in a WMS service has been resolved.

• Spatial operation fix

  • The geometry of the source for a spatial operation wasn't being displayed on the client for all spatial operation types, only the buffer operation was displaying the source geometry.

2.5.18

Released 24 June 2016

Enhancements

• Bookmark grouping

  • Published bookmarks are now grouped based on the user that created the bookmark to try and make the menu less unwieldy.

• Tooltip for redline shapefile export updated

  • The default tooltip for the redline shapefile export has been changed to clarify its purpose.

• Tooltip for redline kml export updated

  • The default tooltip for the redline kml export has been changed to clarify its purpose.

• Current Weave server version available on client

  • As part of the client startup, the current version of Weave is now sent to the browser.

• Zoom to coordinate marker change

  • The marker placed when you zoom to a coordinate is now optionally removed when the panel is closed.

• Reduced logging in user handling

  • Removed some non-important log messages around handlling of user sessions.

• Improved handling of config file reading

  • The config file reader will new report errors with config files via the health api, and also record more detailed information about what file provided the configuration item.

• Additional information available for logging

  • You can now log the username and uid against each record written by the logging system.

• Added support for pageSize attribute

  • All form parameters based on lists now allow you to set the pageSize directly for the parameter (setting it to 0 disables the paging).

• Warning added to map view

  • If you add the same map engine twice to a map view you will now receive a warning, since you should not do that.

• New entity filtering API

  • It's now possible to create a bundle that will filter what entity types are available to the user, this allows more advanced filtering beyond just an acl.

• Filtering of entities via defaults section

  • It's now possible to specify a subset of entity types that should be sent to the browser via the default section in the client config.

• Filtering of entities based on user attributes

  • It's now possible to specify a subset of entity types that should be sent to the browser via user attributes.

• Formatting of data grids

  • It's now possible to specify formatting options for a grid in a <data:data> tag, rather than having to specify it in the grid panel or the defaults section, so it's available to all grids that display the data.

• Modified error handling for AGS tiled map services

  • Tiled map services that return no tiles are now handled the same as a regular map engine that has failed.

• Entity icons in quick search

  • It's now possible to have icons associated with entities shown alongside the results in the quick search.

• Index build feedback

  • Submitting an index build requests now indicates that the command has been submitted, so you at least know that something is happening.

• Spatial intersection data definition enhancement

  • The spatial data definition is now more flexible in the data it can generate.

• Shift pan

  • Now holding down the shift key allows you to pan the map with the mouse regardless of the current tool.

• Spatial identify enhancement

  • The spatial drill down tool will now group entities based on any grouping specified for the entity.

• About action

  • The about action now provides the version number for the server.

• New latitude/longitude formatting

  • There are now additional formatting options for latitude/longitude.

• openExternal now supported per-parameter

  • It's now possible to specify if a url parameter should be opened in an external tab/window, or if it should be opened in an internal Weave tab/window, as a complement for the openExternal setting in the defaults section.

• Entity filtering on the client

  • It's now possible for client code to filter the displayed entities on the fly.

• Field width settings

  • It's now possible to directly specify a parameter width to specify exactly how wide a form field should be.

• Improved handling of file: links

  • file: based links will always be opening in an external tab/window, since they require the support of the browser to work and can't be opened internally.

• Collapse header is hidden by default

  • The extra collapse header is removed by default now, to better match the UI in Weave 2.4, and can be added back by setting hideCollapseTool to false for a layout region.

• Projection panel update

  • The projection panel now outputs an additional format for latitude/longitude.

• Entity highlighting can be set in the map view.

  • Previously each grid related panel would specify how to highlight a selected record, you can now do this once in the map view.

• Data caching change

  • Data generated by a data definition is not longer cached forever by default.

Fixes

• Style menu fix in ToC action

  • The dynamic toc menu created by the toc action button did not handle all map engine types correctly.

• Redline fixes

  • The values shown in the redline style menus did not always match the values of the selected redline item.

• Filename case fix for custom icons

  • Custom icons that had an extension of ."GIF" and ".PNG" (as opposed to .gif and .png) were not being published.

• StreetView fix

  • A minor issue with the Google StreetView panel has been fixed.

• Oracle spatial connection fix

  • A fix for issues that could occur when connecting to Oracle spatial databases has been applied.

• Spatial upload fixes

  • Issues with data uploaded with different coordinate reference systems have been resolved.

• Support dump fix

  • The support dump would fail if the gathering of some database related information failed.

• Dynamic spatial filter fix

  • Spatial mapper filters that utilised user attributes weren't working.

• Form default value fix

  • Setting a default value for some form fields didn't always work.

• Weave map engine fixes

  • The internal Weave map engine has been updated to fix some issues with custom CRS's.

• Dynamic map engine fix

  • The dynamic map engine was incorrectly limiting the available map engines.

• Map parsing fix

  • A minor issue with parsing of the map request from the client has been fixed.

• Custom CRS output fix

  • An issue with logging of custom CRS's has been fixed.

• Highlight fixes

  • Customising the highlighting styles in a grid view was not being applied.

2.5.15.14

Released 13 May 2016

Fixes

• Bookmarks menu fix

  • Sometimes the bookmark menu would get messed up when adding and removing bookmarks.

• Redline slider fix

  • The sliders for the redline opacity and rotation controls would not always represent the underlying value.

• Spatial upload slider fix

  • The sliders for the spatial upload opacity controls would not always represent the underlying value.

• Report input panel fix

  • The report panel wouldn't let you remove an optional text field once the form had been submitted without resetting the form.

• Google street view fix

  • When using the mouse wheel to zoom in or out the StreetView panel would not always be updated with the new location.

• Spatial intersection data connection fix

  • Fixes were applied to resolve issues when performing cross database intersection operations.

2.5.17

Released 13 May 2016

Enhancements

• Map panning with shift key

  • You can now pan the map at any time by holding down the shift key and moving the mouse.

• Selection map engine enhancements

  • There's no longer a requirement to specify the geometry type, either in the selection map engine config or the geometry metadata table, for a layer when Weave can't determine the geometry type itself. Additionally it will now handle layers that have different geometry types in a single spatial column.

• Indexing enhancements

  • The index osgi commands now provide immediate feedback when the command has been submitted.

• Index client API enhancement

  • The index combo box now fires an event before loading the index data, allowing for custom code to modify the index before being performed.

• Improved fail over support for tiled AGS map engines

  • It's now possible to configure a tiled AGS map engine to fail if it can't generate an image rather than returning an empty map, this can then be caught by a dynamic fail over map engine to switch to a different server.

• Added username and uid to logging context

  • It's now possible to include %X{username} and %X{uid} in the logging conversion pattern to include the current users name and/or uid for each line of log output.

• Grouping of published bookmarks

  • The menu that shows published bookmarks now shows the bookmarks grouped by the user that published them, this can be disabled by setting grouped to false in the bookmarks item.

Fixes

• Spatial intersection data connection fix

  • Fixes were applied to resolve issues when performing cross database intersection operations.

• Spatial editing fix

  • Computed attributes weren't being updated when a change was submitted.

• Non-spatial editing fix

  • There was an issue when the non-spatial editing looking for any config item that matched the datastore id, not just a datastore.

• Dynamic map engine fix

  • The dynamic fail over map engine wasn't using the map engines in the order listed in the config.

• Weave map engine fix

  • The Weave map engine handles the situation where it can't determine the underlying CRS from the spatial engine better.

• User monitoring fixes

  • Some fixes were applied to the monitoring of user sessions so that resources were cleaned up properly.

• Map description parsing fix

  • A typo in the code resulted in some new label handling functionality not always being used.

• Bookmarks menu fix

  • Sometimes the bookmark menu would get messed up when adding and removing bookmarks.

• Redline slider fix

  • The sliders for the redline opacity and rotation controls would not always represent the underlying value.

• Spatial upload slider fix

  • The sliders for the spatial upload opacity controls would not always represent the underlying value.

• Google street view fix

  • When using the mouse wheel to zoom in or out the StreetView panel would not always be updated with the new location.

• Report input panel fix

  • The report panel wouldn't let you remove an optional text field once the form had been submitted without resetting the form.

2.5.15.13

Release 4 May 2016

Fixes

• Spatial editing fix

  • Computed attributes weren't being updated when a change was submitted.

• Non-spatial editing fix

  • There was an issue when the non-spatial editing looking for any config item that matched the datastore id, not just a datastore.

• Dynamic map engine fix

  • The dynamic fail over map engine wasn't wasn't using the map engines in the order listed in the config.

• Weave map engine fix

  • The Weave map engine handles the situation where it can't determine the underlying CRS from the spatial engine better.

• User monitoring fixes

  • Some fixes were applied to the monitoring of user sessions so that resources were cleaned up properly.

• Map description parsing fix

  • A typo in the code resulted in some new label handling functionality not always being used.

2.5.16

Released 14 April 2016

Enhancements

• Encryption of passwords in security.xml

  • It's now possible to encrypt the passwords stored in security.xml.

• Selection storage API

  • There's a new server API that allows you to perform filtering when updating selections on the server.

• Undo last selection

  • There's a new tool for the client, weave.selection.Undo, that when added as an action item to a toolbar will allow the user to undo the last selection operation.

• Dynamic map engine update

  • It's now possible to switch between map engines depending upon if a layer is visible or not. Previously this was only available with ArcIMS, but now you can create a dynamic map engine and do this for any map engines. This is used to do things like switch from PNG and JPEG when turning on an aerial photography layer to save bandwidth, or to adjust the contrast on vector layers when turning on an aerial photography layer.

• Client StreetView API enhancement

  • An event is now fired when the StreetView library is ready for use.

• Client ToC Node API enhancement

  • It's now possible to register for an event that's called before a click is processed for a ToC entry, allowing the listener to perform some processing or stop the event from continuing.

• Client Map Panel API update

  • Events are now fired when there is a problem loading a map image.

• Overview map enhancement

  • It's now possible to specify more than one map engine for the overview map component.

• DMS enhancement

  • A DMS provider can now be configured to include an ACL, thus allowing restrictions on the documents returned to a user.

• Custom stop words for quick search index

  • It's now possible to specify your own list of stop words when building a quick search index.

• Improvements in BIRT error reporting

  • If there's an error when generating a BIRT report more information will be included in the weave.log file to try and help resolve the cause.

• Authority integration enhancements

  • The Authority integration now has an extra option for configuring the neighbour notification function, allowing Weave to use a buffer spatial operation, of a configurable distance, rather than a strict touches spatial operation.

• WFS spatial engine

  • There's a new WFS spatial engine available that performs better than the previous version.

• Quick link context menu

  • A new map view context menu item is available to quickly open an external URL that contains the id (or another attribute) of the entity that the user clicked on.

• Disable wrapping of text in the ToC panel.

  • The ToC panel, and probably any other tree based panel, will no longer wrap the text labels.

• Grid panel highlight enhancement

  • If a record in a grid panel contains an 'x' and 'y' (or 'lat' and 'lon', or 'latitude' and 'longitude') fields then values from these fields will be used to place the highlight marker rather than centroid/boundary of the associated entity when the record is selected in the grid panel.

• Map image export enhancement

  • It's now possible, in the config for the tool, to specify the format of the generated image. The default is still png, but it's now possible to use other formats supported by Weave, e.g. jpg. Only one format can be specified for the button, but multiple instances of the button can be added to an "Export" menu with each button having a different format set.

• Multiple columns in legend component in reports

  • The BIRT legend control now allows you to specify the number of columns to use for a legend.

• Redline text improvements

  • Support for multiline labels, text rotation and individual text items has been added. Multiline labels are enabled by setting multilineLabel true in the clients redline config, and the rotation is accessed via the font menu.

• Redline buffer tidying

  • The new redline buffer tools have been tidied up a little and made more consistent.

• Caching of client configuration

  • Caching has been implemented in the server for the client configuration, which should result in improved startup time. At this stage it's only for anonymous users.

• Coord zoom enhancement

  • The coord zoom tool has been enhanced to work with decimal degrees better.

• ToC panel enhancement

  • It's now clearer when a layer isn't available in the toc panel.

• DB session storage update

  • It's now possible to configure user database storage via the Weave config, rather than requiring a system property.

• Duplicate items in config files

  • Weave will now generate an error and not process a duplicate (same namespace, type and id) config item.

• Added support for url parameters in map tips.

  • The map tip popup will now stay around for a couple of seconds after the user moves the mouse, giving them time to click on a links in the popup.

Fixes

• Map redraw fix

  • If no transitionEffect option was explicitly specified for a map engine the map layer will disappear when it was being redrawn, resulting in a blank map panel while the client was waiting for the server to generate the new image. This fix ensures that the original image will be displayed until the new image is available. The transitionEffect can be disabled, and you'll get the blank map while waiting for a redraw again, by setting the transitionEffect value to 'none', this may be required if you need to support really old versions of Internet Explorer.

• Edit bundle fix

  • The delete button in the spatial edit panel was enabled when it should be disabled and vis-versa.

• Map caching fix

  • Generated map images were not having their browser cache setting applied correctly causing more map re-draws than was necessary.

• ToC folder issue

  • Folders in a table of contents were registering click events and causing the map to change when they shouldn't have been.

• Startup tip issue

  • Displaying a tip at startup would result in anything behind the tip not being accessible when the tip was removed.

• Redline label editing fix

  • The delete and backspace keys were not recognised when updating the on-screen label for a redline object.

• DMS link fix

  • The URL's in the page listing available document was not always encoded correctly.

• WMS image format fix

  • If the image format for a WMS request contained spaces then the generated URL was invalid.

• GeoTools library update

  • The core GeoTools library has been updated with resolves some internal issues.

• Data export update

  • Sometimes the exporting of data from the grid panels was displaying the data directly when it should have been offering to save or open the data.

• Tiled map service caching fix

  • Sometimes the location of the tile cache would be incorrect.

• Double click selecting map

  • When using a tool that requires a double click to finish the operation in some versions of Google Chrome this would select the map content.

• Report map generation fix.

  • If a single map engine failed while generating a map image for a report then none of the maps would be displayed.

• OSM tile fix

  • Open street map services that didn't serve tiles at 256 x 256 pixels wouldn't display properly in reports.

• Geometryless spatial engine fixes

  • A number of fixes have been applied to the geomtryless spatial engine.

• Redline loading fix

  • An issue that stopped the loading of previously saved redlines has been fixed.

• ToC loading fix

  • An issue where a parent group would be turned on after being restored, even if it was turned off when it was saved, has been fixed.

• Apache reverse proxy fix

  • A bug in Apache when used as a reverse proxy resulted in less than optimal caching, a workaround has been implemented in Weave to help.

• Fixed issue with session cleanup

  • User sessions weren't being clean up properly, not an issue unless you're using database session storage.

2.5.15.12

Released 17 February 2016

Fixes

• Geometryless spatial engine fixes

  • A number of fixes have been applied to the geomtryless spatial engine.

• Redline loading fix

  • An issue that stopped the loading of previously saved redlines has been fixed.

• ToC loading fix

  • An issue where a parent group would be turned on after being restored, even if it was turned off when it was saved, has been fixed.

2.5.15.11

Released 5 February 2016

Fixes

• Report map generation fix

  • If a single map engine failed while generating a map image for a report then none of the map would be displayed.

• OSM tile fix

  • Open street map services that didn't serve tiles at 256 x 256 pixels wouldn't display properly in reports.

2.5.15.10

Released 3 February 2016

Fixes

• Tiled map service caching fix

  • Sometimes the location of the tile cache would be incorrect.

• Double click selecting map

  • When using a tool that requires a double click to finish the operation in some versions of Google Chrome this would select the map content.

2.5.15.9

Released 28 January 2016

Fixes

• GeoTools update

  • The core GeoTools library has been updated after they released a number of fixes.

• Data export update

  • Sometimes the exporting of data from the grid panels was displaying the data directly, when it should have been offering to save or open the data.

2.5.15.8

Released 21 January 2016

Fixes

•  DMS link fix

•  

  • The URL's in the page listing available document was not always encoded correctly.

• WMS image format fix

  • If the image format for a WMS request contained spaces then the generated URL was invalid.

2.5.15.7

Released 11 January 2016

Fixes

• Redline label editing fix

  • The delete and backspace keys were not recognised when updating the on-screen label for a redline object.

2.5.15.6

Released 14 December 2015

Fixes

• Map redraw fix

  • If no transitionEffect option was explicitly specified for a map engine the map layer will disappear when it was being redrawn, resulting in a blank map panel while the client was waiting for the server to generate the new image. This fix ensures that the original image will be displayed until the new image is available. The transitionEffect can be disabled, and you'll get the blank map while waiting for a redraw again, by setting the transitionEffect value to 'none', this may be required if you need to support really old versions of Internet Explorer.

2.5.15.5

Released 11 December 2015

Enhancements

• Encryption of passwords in security.xml

  • It's now possible to encrypt the passwords stored in security.xml.

2.5.15.4

Released 11 December 2015

Fixes

• Edit bundle fix

  • The delete button in the spatial edit panel was enabled when it should be disabled and vis-versa.

2.5.15.3

Released 10 December 2015

Fixes

• Map caching fix

  • Generated map images were not having their browser cache setting applied correctly causing more map re-draws than was neccessary.

2.5.15.2

Released 10 December 2015

Fixes

• ToC folder issue

  • Folders in a table of contents were registering click events and causing the map to change when they shouldn't have been.

2.5.15.1

Released 10 December 2015

Fixes

• Startup tip issue

  • Displaying a tip at startup would result in anything behind the tip not being accessible when the tip was removed.

2.5.15

Released 2 December 2015

Enhancements

• DataWorks integration

  • It's now possible to specify an id filter to be used when communicating with DataWorks.

• Redline tools

  • Two new tools for generating buffers around redline objects have been added.

• Google map view

  • Updated the Google map view panel so that it supports the additional zoom levels that are now available for the terrain layer type.

• Client API update

  • Allow client code to open an external window with a name so it can be reused.

• Map panel API update

  • Pass the mouse screen x, y location to context menu click handers.

• Connection monitor API update

  • Provide an additional error callback function for monitoring connection attempts failures.

• Database connection update

  • Added support for the Health Check API to database connection so they can be externally monitored.

• Health check update

  • The health check URL now supports additional output formats, xml, json and plain text, plus the original html.

• WMS map engine update

  • Added support for the Health Check API to WMS based map engines so they can be externally monitored.

• WMS client publishing option

  • A new experimental option to have the client directly connect to WMS map engines has been implemented.

• Selection filter logging update

  • More logging has been added to selection filtering to help resolve any configuration issues, previously some useful information was being hidden.

• Get/Set selection request update

  • The server handlers for getting and setting a selection on the server can not also supply a filter when performing the operation, this allows on the fly translation of the id's.

• Spatial engine update

  • Added support for the Health Check API to spatial engines so they can be externally monitored.

• Support API update

  • Some new classes to help working with HTTP request headers have been added.

• Hansen integration update

  • Additional checks have been added to validate the Hansen configuration, along with additional logging to help catch errors.

• GeoTools update

  • GeoTools has been updated from release 13.3.

• OpenLayers update

  • OpenLayers has been updated to release 2.12.

• ArcGIS Server update

  • The ESRI ArcGIS Server libraries have been updated to 10.3.1.

• Added ACL's to indexes

  • It's now possible to set an ACL for an index to allow or deny access when performing a search.

• KML export update

  • The Zip'n'ship KML exporter will now set a placemark name of the exported feature has a "name" attribute.

• Spatial engine configuration update

  • The Oracle Spatial, SQL Server and PostGIS drivers have all been updated so that the information stored in the geometry and primary key metadata tables can be set directly in the Weave config.

Fixes

• Get and Put action

  • Fixed an issue where only one of the selection get or put actions would be visible at a time.

• ArcGIS legend fix

  • Some time layer scale ranges weren't being honoured when drawing a legend.

• Map engine init handling fix

  • Weave could miss some map engines definitions that need to be sent to the client at startup (when using a server tag in a client map engine).

• KML export

  • The attributes exported with KML were slightly mis-configured causing the start of attributes to also be displayed into the table of contents in Google Earth.

• Oracle Spatial fix

  • The embedded Oracle JDBC driver was updated to resolve an issue with Oracle Spatial.

• WMS Server i18n fix

  • The Weave WMS server was reporting that it was sending it's response using UTF-8 encoding, but it was actually using ISO-8859-1.

2.5.14

Released 13 October 2015

Enhancements

• Client API update

  • It's now possible to directly trigger a tool/button from external JavaScript.

• Spatial engine connection enhancement

  • If a spatial engine is not available when Weave starts it will now continue trying to connect rather than just ignoring it. Plus, if validateconnections is set to true Weave will periodically check that the connection is still alive.

Fixes

• Bookmarks fix

  • The bookmark components were not acting correctly when they were being called directly.

• Trim update

  • The Trim interoperability module will handle the situation were the id's sent from Weave are not unique better. This was in 2.4 but got lost in the move to 2.5.

2.5.13

Released 9 October 2015

Enhancements

• Client legend enhancement

  • If the map engine supports it, currently only QGIS, the client legend can be setup to only display entries for items within the map extent.

• Client API update

  • There's a new Weave.relativeUrl(url) method that will generate a proper relative url, for use when Weave is embedded in another page.

• Timeout and error handling for spatial operations

  • It's now possible to individually specify timeout values for each spatial operation, and the client handles the timeout and other errors better.

• Buffer performance improvement

  • The buffer operation has been optimized to perform better.

• Removal of layer labels

  • If the map engine support it, currently only a custom QGIS, the client can turn off and on labels for individual layers.

• Non-spatial editing update

  • Null values are handled better when performing an update.

• Updates for support dump.

  • The support dump now sorts some items to make it easier to compare two separate dumps, plus it also outputs information about the registered entities.

• Updater update

  • The updater now updates all components that have been installed, including the edit and interop components, as well as the core components.

• New JSON support API

  • A new API for performing common JSON operations is available on the server.

Fixes

• DMS fix

  • Some URL's that the document management system produced were not correctly encoded so would cause issues with non-url safe characters.

• JSON error fix

  • Removed some error messages that were logged when marshalling/un-marshalling JSON objects internally.

2.5.12

Released 26 September 2015

Enhancements

• Weave WMS map engine update

  • It's now possible to choose a different colour for the highlight marker when highlighting a point.

• Support for HTTP redirects with WMS/WFS

  • If a WMS or WFS server responded with a HTTP redirect then Weave will correctly download the redirected resource.

Fixes

• Fix for client map engine scale ranges

  • If a scale range was specified for a client map engine the map may have still drawn when generating an image on the server.

• SQL selection drawing performance issue

  • SQL Server, and maybe other databases, were taking too long to render selections, previously setting the batchsize for the selection map engine would fix the problem, but this is no longer required.

2.5.11

Released 23 September 2015

Enhancements

• i18n updates

  • Additional text in the client can now be internationalised.

• A new client production script is available

  • When embedding Weave in another web page it's not possible to retrieve a single script that contains all of the code required by Weave.

• Authentication updates

  • It's not possible for the web application container to provide the user authentication, rather than Weave performing it.

• New table join option for data definition

  • There's a new "join" tag available for data source data definition that makes it possible to specify a table join, rather than having to use "from" and "where" tags. It also allows you to specify the join type.

• Non-spatial editing update

  • Support for editing views has been improved.

• Indexing improvements

  • The algorithm for finding documents with the quick search has been updated to return better results if the initial query doesn't find anything.

• WMS map engine connection enhancement

  • The WMS map engine handles the situation where a service initially accessed via http switches to https.

• WMS map engine error enhancement

  • If a WMS map server generates an error Weave will try and determine if it's a particular layer that's causing the issue and try and generate a map without the bad layer(s).

Fixes

• Fixed issue with legend

  • The legend would display all items when asked to only show those that were visible and no items were visible, rather than showing nothing.

• Fixed issue with cursor

  • The cursor wasn't changing to the correct pointer in some situations.

• Minor authentication fixes

  • A couple of locations were using an old, but still working, method for determining if the user was anonymous or not.

• BIRT report fix

  • There was a problem where some report parameters were not being set correctly.

• Upload fix

  • If the upload map engine was not included in the client map view then the upload would not display, this was not supposed to be required any more and has been fixed.

• Logging update

  • A bunch of useless errors were being logged during startup and are no longer reported.

2.5.10

Released 20 August 2015

Enhancements

• GPX upload support

  • Added support for uploading GPX file via the spatial upload function.

• DataWorks added to installer

  • The DataWorks bundle wasn't included as part of the interoperability installer, now it is.

• Data definition lists updated

  • list type parameters in a data definition now allow you to specify which parameters in the lists source data definition contain the label and values to use for the list, by setting labelColumn and valueColumn. The implementation is also now smarter about which columns it uses if you don't specify these new values. Finally it now works just generally works more consistently.

• Index builder update

  • It's now possible to specify how many indexes can be built at once, previously only one index would be built at a time to reduce load on the server and back end data sources, no you can set a system property weave.index.threads to the number of indexes that can be built at the same time.

• Login page update

  • The login page now looks better when used on a small screen, e.g. a phone.

• Installer update

  • The Weave installer now allows you to specify the servers proxy setting during installation.

Fixes

• Fix for Pictometry

  • The Pictometry bundle was updated to work properly with 2.5.

• Fix for the file system docstore API implementation

  • The default implementation of the docstore API, that stores persistent document in the local file system, would eventually cause the Weave process to run out of file handles and fall over (yes that is as bad as it sounds, if you're running 2.5.9 then you need to update to 2.5.10).

2.5.9

Released 11 August 2015

Enhancements

• Google map view update

  • Added the ability for a user to customise the Google Map style easily in the config.

• Map view navigation update

  • Added support for click events in the Navigation control.

• Update to the Weave map engine.

  • The internal Weave map engine now supports specifying exactly which CRS's you want to expose.

• Updated support dump

  • The osgi dump command now also includes spatial engines, data sources and health checks in the dump it generates.

• Weave WMS server update

  • The Weave WMS server now understands URL's that contains duplicate parameters that should really be combined as a single parameter (the URL's are technically invalid according to the WMS specification, but because some clients generate them the Weave WMS server will now handle them correctly).

Fixes

• Fix for WMS styling

  • There was a small issue when switching styles if the default style was not the first one listed.

• Fix for right-click menu in client

  • The handling of right click context menus in the client had problems if the client was embedded in another web page.

• Fix for Compass Image Transparency Sliders

  • The extended image transparency sliders weren't working correctly when used with 2.5, they have now been updated and also included as an official part of 2.5.

• Fix for Informix generated SQL

  • The SQL generated by Weave for some situations on an Informix database was incorrect.

2.5.8

Released 23 July 2015

Enhancements

• Improved support for server clustering

  • Internal changes have been made to Weave to help support running Weave on multiple servers with load balancing and fail-over.

• Bookmarks client update

  • The bookmarks client UI has been updated to handle i18n resources in a more consistent manner.

• Improved support for client embedding

  • Internal changes have been made to Weave to help support embedding Weave inside another web page.

• New API for sending document to the client

  • A new internal API is available for encapsulating how documents can be sent back to the client. For example, now rather that just streaming a PDF directly back to the client the server can specify that the file be persisted and a URL pointing to the save document be sent to the client instead. This sort of stuff was previously performed by by each plugin that required the functionality, but is now provided by a single API which hides the complexities.

• Update to config.xml reader

  • The code responsible for reading the config.xml file (and the files it includes) has been enhanced, firstly to make it's internal API more open so that additional configuration sources can be used, and secondly, this new API has been used to provide a way to load configuration information from a web server.

• Report generation enhancement

  • Reports can now be streamed (or stored) directly, without having to be first generated in memory. This will help with memory usage when generating BIRT reports.

• Report Map generation enhancement

  • It's now possible to turn off the highlighting of the current entity when generating a BIRT report.

• WMS default style enhancement

  • When determining which WMS map layer style to use as the default Weave will no longer just use the first, it will try and determine if one of the other is a better option.

• New simpe HTTP client API

  • A simple HTTP API for issuing GET/POST requests is available on the server. It's a lot lighter and simpler that existing API's that are currently being used internally, and provides a quick way to retrieve content from an external web server (for example WMS legend images, and remote configuration files)

• Indexing highlighting enhancement

  • Keywords can now be highlighted in the displayed search results (add highlight="true" to the index combo component configuration).

• Indexing API enhancement

  • The indexing API now provides additional search methods.

• Ping request

  • The server now supports a simple "ping" requests that can be used by external tools to see if the server is alive.

• Heartbeat update

  • The client heartbeat requests now stop after a certain amount of time if the server isn't responding and the period between heartbeat requests grows gradually during this time.

• KML upload

  • Uploading KML files is now more forgiving in the formatting of the files that it will accept.

• Client provide update

  • The new client provider bundle has been updated to auto-generate the JavaScript non-debug code from provided debug classes, and now supports compression of the non-debug JavaScript code.

Fixes

• Bookmark client update

  • Applying a saved bookmark is now more robust.

• The document storage API update

  • The implementations of the new document storage API now remove expired documents.

• Update for the 'dbmd' command

  • The osgi dbmd command will no longer fall over if it's presented with a CLOB or BLOB column when describing a table.

• Fix for the Weave map engine

  • Multiple layer styles, introduced in 2.5.6, cause Weave map engines to stop working if they had no styles defined.

• Fix for buffer operations

  • Some server operations that generated a buffer with zero distance would fail.

• ArcGIS legend fix

  • Client legend items from ArcGIS Server were being displayed even if the layer was outside of it's visible scale range.

• Indexing fix for user attributes

  • An index that uses user attributes now works properly when there are spaces in the user attributes.

2.5.7

Released 12 June 2015

Enhancements

• New tiled map engine

  • The support for tiled map engines, initially based on GeoWebCache but allowing future support for others, had been added.

• New document storage API

  • A new internal API has been added that provides a way for server code to persistently store a "document" for later use. For example this allows us to generate a report and provide a fixed URL to the user so that they share the generated report with other users.

Fixes

• Fixed issue with some spatial operations

  • Release 2.5.5 updated some spatial operation to use an "overlays" rather than "intersects" spatial operation, but this ha caused some inconsistencies so has been reversed.

2.5.6

Released 9 June 2015

Fixes

• Fixed issue with empty i18n resources.

  • If there was no content for a specific i18n client resource then none of the resources in the set would be processed. Now an empty resource will be treated as an empty string, as it should have been al long.

• Fixed issue with multiple layer styles.

  • In some circumstances the legend would not update because of a change made in the last release related to multiple layer style support.

2.5.5

Released 5 June 2015

Enhancements

• Support for multiple layer styles

  • If the underlying map engine supports multiple styles per layer it's now possible for the client to switch between them. Currently only the WMS and Weave map engines support multiple styles.

• Client redline startup parameters

  • It's now possible to add items to the redline layer at startup using URL parameters.

• New selection identify tool

  • There's a new tool that performs an identify operation using a spatial drill with the geometry of the currently selected feature.

• Spatial select tool update

  • The spatial selection operation tool now has two options for an intersect, depending upon if you want to selected features that touch or don't touch the source geometry.

• Context menu update

  • Now when a context menu is displayed any clicks outside of the context menu itself will just close the context menu, they will not register as mouse clicks on what ever it was you clicked on.

• Tooltip support for menu items

  • Menu items can now have their own tooltips.

• 'showLoading' available as a global option

  • The showLoading setting, to re-enable the loading bar when a map engine is drawing, is now available at the map view level, rather than having to be set for each map engine in the view.

• Grey theme updates

  • The grey theme has been tweeked a little to make it a little clearer and tidier.

• Multiple style support for Weave map engine

  • The internal Weave map engine now supports multiple styles per layer.

• OSGi dbmd command update

  • The dbmd command can now generate an attribute search config for a table, and it also filters out system items when listing tables.

• Reduced memory usage with user attributes

  • A small optimisation of the user attributes code means it will use less memory when performing attribute substitution.

• Enhanced WMS map engine image format verifier

  • When Weave contacts a WMS server that says it supports PNG images Weave will try and determine what type of PNG image that it actually generated (8, 24 or 32 bit for example). This is generally done by generating a small map image using just the first available layer. If this isn't the correct layer to use then the name of the layer can now be changed, using the <formatLayer> tag (setting the value to the name of the WMS layer to use), or it can be disabled all together using the <checkFormats> flag (setting the value to false).

• Spatial editing bundle updates

  • You can now specify that a spatial edit supports more than one type of geometry, but only one type at a time. By default, audit records are written when a create, update and/or delete is performed. It is now possible to restrict the writing of an audit record to one or more of the create, update, delete edit modes.

• Postgres Driver Update

  • The JDBC driver used to connect to PostGIS has been updated to the latest version 9.4.

• New Document Storage API

  • A new API for storing documents has been added. This new API makes it possible for Weave to store content permanently, i.e. reports can be generated and stored and a persistent URL provided to the client. Initially this API is not exposed to the client, but is available for future use.

• The Weave WMS server is now provided by default.

  • The ability for Weave to act as a WMS server was previously available by manually downloading and installing the correct bundles, these bundles are now included in Weave as part of the default install (or a 2.5.5 upgrade).

Fixes

• Client WKT parsing fix

  • There was an issue with the client parsing WKT multi-point features when the individual coordinates weren't enclosed in parentheses, this is now fixed.

• Client parameter parsing fix

  • The client wouldn't parse multiple URL parameters with the same name, only the last parameter would be used, now all parameters are parsed correctly.

• Server startup issue

  • An issue where the server would not start if the installation path has spaces in it has been resolved.

• Spatial filter parsing issue

  • A filter generated for an attribute named "ID" would fail.

• Export failing on client

  • The grid export tool wasn't working properly.

• CQL filter parsing update

  • The parser that handled generating spatial filters from text had some issues parsing filters that included an ID column.

• Mail sending fix

  • The code to send an email from within Weave was not working correctly.

2.5.4

Released 24 April 2015

Enhancements

• Client error reporting update

  • On supported browsers a JavScript error will now dump the call stack to the browser console, which will help target the source of the error.

• Coord Zoom panel update

  • The coordinate zoom component will now remember the coordinates enters when switching between coordinate reference systems.

• Map context map update

  • When displaying the map panel context menu the map panel will no longer respond to click while the menu is open.

• Maptips update

  • You now have more control over the size of the map tips balloon.

• Measure tools

  • You can now specify a coordinate reference systems for the measure tools.

• New navigation tools

  • There's three new navigation tools that support navigation when clicking and dragging, but selection when single clicking.

• Simple report menu update

  • The simple report menu now supports more configuration options.

• CommsSvr update

  • The client component responsible for communicating with the server has been enhanced to improve error reporting and to be a little more flexible.

• New dynamic loading component in the client

  • The browser client now has a standard way to dynamically load resources at runtime, which eventually should help client startup time as other components start loading their resources as they need them rather that trying to load everything at startup.

• Form field updates

  • An enhancement to list boxes make it possible to make proper combo boxes.

• New form field type

  • There's now some support for 'money' field types.

• Grid panel highlight update

  • You can now configure the symbology of the map highlighting.

• Sorting added to data definitions

  • You can now specify a default sort order for data definitions.

• New Health API

  • There's a new API that allows various system components to report their current health status, so you can see at a glance where there may be issues within Weave. Currently only the new non-spatial editing bundle uses the API but in the future more bundles will be updated to make use of it.

• New non-spatial editing bundle

  • There now support for directly editing database tables.

• Update to index building

  • It's now possible to configure an index to build the geometry first then the attributes, or the attributes first then the geometry. Since changing this could result in a different final index it now possible to set a flag in the index configuration to specify that the geometry should be processed first (which used to be the default) rather than the attributes being processed first (which is now the default).

• Update to the parameter API

  • The API used to represent parameters now has support for a money type, and also a new API for traversing a collection of parameters using visitors.

• Request handler update

  • The base request handler now includes support for generating a json result that can be used as a callback, e.g. a jsonp result.

• Script provider update

  • Bundles that provide scripts to execute client requests can now also be provided by an OSGi service, and not just from an Eclipse plugin.

• Internal data provide API update

  • The API used internally to interact with data definitions in scripts had been tidied up a little to make future enhancements easier to implement.

• Buffer operations update

  • Buffering operations now provide more control over how the buffer can be performed, e.g. the spatial operation that's performed with the final buffer can be tuned.

• Heartbeat servlet update.

  • The URL used for the heartbeat request from the client can now be tuned to allow it to be called from another system, rather than just the Weave browser client, which would help for example to allow it to be used from a third party monitoring system to determine if the Weave server is still up. Adding validate=false to the URL will disable the session validation of the request. Plus the response can be in a json format if requested.

• Config file reader update.

  • Now if there's an error in a comment in a config file only up to 100 characters will be output (first and last 50) if the comment is larger than 100 characters.

• Additional spatial operations available

  • A more complete set of spatial operations is now available (contains, overlaps and within were added) for code using the spatial operations API.

• Update to spatial engine registration

  • A spatial engine can now be registered using a deferred registration process, this allows, a data source implementation to call back into the registration process to indicate when the data source has been created, rather than the startup process having to wait for the data source to be created during the startup process.

• Filter utility class update

  • The FilterUtils helper class has been updated to better resolve situations where it's creating filters from other filters, for example creating an AND filter from two other filters will handle the situation in a more sensible fashion when one or both of the source filters are Include or Exclude filters, or they're null.

• Spatial edit bundle updates

  • The spatial editing bundle now support combo boxes better and performs client input validation in a better way.

• New JDBC helper API

  • There's a new internal API available for working with JDBC, it provides a range of useful functions for when working directly with JDBC connection, plus a new JDBC object name validator class, which is useful for validating table names, etc, used in config files.

• ArcSDE spatial engine update

  • The ArcSDE spatial engine config now allows you to specify is un-registered tables should be included.

Fixes

• DataWork update

  • A fix for an issue when sending a selection to DataWorks.

• Interop

  • The a number of interoperability components were updated to work better with newer versions of IE.

• Redline

  • The delete and delete all redline actions had their i18n resource identifiers fixed.

• Image transparency slider

  • The slider was updated so that it doesn't cause problems when used with map layers that don't support transparency.

• Ad-hoc query builder update

  • The Ad-hoc query builder component had its UI tidied up and some of its resources internationalised.

• Earthmine fix

  • The Earthmine component has had a problems with the height not being set correctly in newer browsers fixed.

• Redline text spacing fix

  • An issue where a redline label on the client wouldn't match a report was fixed.

• Navigation history tools fixes

  • The next and previous navigation tools weren't working when used in a context menu.

• Clear all selection fix

  • The clear all selection button had an issue that stopped its tooltip from being set.

• Fix for the set selection client action

  • The code from the 'weave.setSelection' action wasn't firing the correct event when the selection update resulted in the selection size being zero.

• ToC scale range fixes

  • Sometimes the toc panel entries would not match the scale ranges from the map engine

• ToC entry change fix

  • Previous versions of Weave allows the toc entries to have their state changes when they were out of range, this is been re-introduced after disappearing for a while.

• Grid action fix

  • Sometimes actions in the grid panel would fire twice.

• Tooltip fix

  • On some browsers tooltips were being wrapped when they shouldn't be.

• ArcGIS Server tiled map engine fix

  • The code that determines which zoom level to use has been fixed to work on older browsers.

• URL search fix

  • The handling of url parameter to execute a search at startup has been made more robust.

• Grid panel highlight fix

  • The map highlighting of features selected in a grid panel has been fixed for multi part geometries.

• Heartbeat fix

  • A long standing issue relating to the heartbeat request causing client restarts has been fixed.

• Nearmap fix

  • Some issues with the Nearmap component has been fixed.

• Spatial filter fixes

  • Touches and Overlaps filters were reversed.

• Update to ToC config generator.

  • The memd toc command would generate layer id's with spaces, which it no longer does. It also now outputs the result to the console rather than the log file.

• Database parameter fix.

  • The 'uppercase' attribute for database parameters wasn't being set correctly.

• BIRT parameter handling fix

  • Grouped parameters weren't being sent to the report correctly.

• Restart command fix.

  • The console command to restart Weave (when it running as a service/daemon) wasn't working properly.

• ArcSDE filter fix

  • The 'touches' filter in the ArcSDE library does not appear to work correctly, so a workaround had been implemented so it does.

• GeoTools data source driver update

  • The GeoTools driver bundles are no longer marked as being singletons, which make it possible to update them in a running system.

2.5.3

Released 16 February 2015

Fixes

• Resolved some minor client issues.

2.5.2

Released 4 February 2015

Fixes

• Resolved issues with ArcGIS Server on Windows.

• Resolved issues with running on Java 8.

2.5.1

Released 22 January 2015

Fixes

• There were a handful of minor issues with the initial 2.5.0 release that were resolved.

2.5.0

Released 31 December 2014

Enhancements

• Updated the underlying third party libraries Weave uses.

  • This includes the BIRT reporting engine, the GeoTools spatial library and the Ext.js client UI, as well as the OSGI platform that Weave runs within.