Content Comparison

2.4.

...

14

Pending Release

Enhancements

...

• A new tool for the creating redline buffers has been added (was supposed to be in 2.4.11 and 2.4.12 but got missed, again!).

...

• The configuration for the selection map engine has changed slightly.

...

• The default which was PNG8 has been changed to PNG32.

...

• It's possible to override some parts of the capabilities document in a WMS map engine.

...

• If debugging is enabled in the client config more error information is generated.

...

• I18n resources can be defined in external properties files, not just <resources> tag in the config.xml file.

...

• The search panel content can be updated to use local language resources.

...

• When in debug mode the client will provide more useful error information when a startup error occurs.

...

• There's now a component that allows display of the current userid easily in the client.

...

• Previously only information returned for client initialisation could use client resources to localise content, now it's possible to turn this on for every response from the server, by setting a 'weave.i18n.all' system property to 'true'.

...

...

• The spatial upload tool no longer requires a toc to be explicitly configured.

...

• The configuration for the details panel is now more flexible and is better at reporting any errors.

...

• Details panel can be configured either with multiple detail tags, or a single details tag containing multiple detail tags. This improves reuse of this information in multiple details panels using config snippets.

...

• You can now use LDAP as the provider of role/group information without requiring it to be used for authentication.

...

• Have updated support for internationalising text, mainly in the grid panels.

...

• The same log values (ERROR, WARN, etc) can be used in logging.properties when configuring log4j and/or java.utils.logging loggers. Previously these two systems had slightly different values.

...

• Removed re-loading of selection rendering configuration on each map draw.

...

• When overriding the geometry type for a layer in the selection renderer <entity id="suburbs">polygon</entity can now be used instead of <suburbs>polygon</suburbs, which removes the "unknown" tag names (based on entity id) in the config. This also applies when overriding the renderer using SLD or CSS.
• The configuration tags no longer need to be contained in an override tag, they can all be listed at the top level of the selection map engine configuration.

...

• It's possible to override the layer list reported by a WMS map engine (to help with dodgy WMS servers).

Fixes

...

• If map updates were disabled when a selection change occurred the change would not be reflected when updates were re-enabled.

...

• Some logging configurations resulted in a lot more output that was expected.

Fixes

...

• The neighbour operation now works correctly for geometry collections.

...

• Ensure that the legend panel was not being initialised more than once.

...