Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

2.4.

...

19

Pending Release

Enhancements

...

  • The client legend related components can have their tool tip text set through client resources.

...

  • The way background services are shutdown has been improved to ensure that things stop in a more controlled manner.

...

  • The version of the Google API used in Weave has been updated.

...

  • The client now reports the id of the server command that failed.

...

  • A new type of id filter, used when sending/receiving id's from a third party system, provides for adding/removing prefixes and suffixes to/from ids. Additionally a filter chain can also be setup, to combine multiple filters into one.

...

...

  • The log now reports the map engine id to make it clearer which map engine has a problem.

...

  • Specifying the map component size in pixels is supported.

...

  • You can start typing to filter the client configuration listed on the index page.

...

  • A new method of allowing third party applications to start Weave is available via a new interop.html page.

Fixes

...

  • The quick search panel was calling the parent constructor from the wrong class, it didn't cause any problems but it's been fixed anyway.

...

  • A recent update to the weave.war file stopped the console from starting locally, it was only started remotely on port 9998.

...

  • A race condition would sometime result in map engines not being registered properly after a server restart.

...

  • Some mail related bundles have been updated to ensure that mail functionality works correctly.

...

  • Lockable layers could not be unlocked.

...

  • The index search was only returning the first page of results.

...

  • The WMS map engine was only generating png images.

...

  • Sometimes the optimal format for map component wasn't being used.

...

  • The mime type for the scalebar wasn't being set correctly.

...

  • The number of threads used to fetch AGS tiles has been set to 1 by default because sometime using more would crash AGS.

...

  • When updating an ArcIMS and WMS map engine configurations make sure that any existing connections are removed.

...