21/02/12staticsecurity plug-in 1.9.0 released

Version 1.9.0 of the staticsecurity plug-in has been released.

This version includes many changes, including

03/02/12back-end 1.10.0 and Geotools layer 1.9.0 released

This version includes many changes, including:

  • use SLD for feature style definition
  • support for features with empty geometry
  • update to GeoTools 2.7.4 (with some additional patches) 
  • new LegendImageService
  • added synthetic attributes and label expressions
  • many usability improvements, added configuration options and bug fixes

Back-end release notes:

03/02/12plug-in updates

We have released updates for many plug-ins:

  • geocoder plug-in 1.2.0
  • printing plug-in 2.2.0
  • hibernate layer 1.9.0
  • wms layer 1.9.0

The most notable improvement is the ability to cahe WMS layers. In general, the changes are mainly usability improvemens, documentation and bug fixes.

Release notes can be found in JIRA:

29/01/12Geometry, API and SLD projects released

Withing the Geomajas spatial application framework, we have released some some generally usable code as separate projects. These projects have no dependencies on other parts of Geomajas and can easily be reused. To facilitate the adoption, these projects are released using the Apache License v2.


The Geometry project contains a DTO class for representing a geometry and services for manipulating these geometries. These objects can be used in various environments, including GWT. They can also easily be serialized to and from JSON.


21/12/11Status update

We wanted to give everyone a heads up on the current status and the near future for the Geomajas project. We have been working so hard these last couple of months that it seems we haven't provided proper updates on what's going on.

Time to rectify that situation. What it all comes down to, is that we are aiming for a 1.10.0 release for the backend and GWT face in januari 2012. This release will also feature a few new plugins, such as rasterization, and SLD support. It's mainly these 2 plugins that are the cause of the huge workload we had to endure lately.

08/09/11Hibernate layer 1.8.1 released

A rather serious bug was found in Hibernate layer 1.8.0 so a bugfix release was built.

It is also available using geomajas-dep 1.11.36

11/08/11GWT face 1.9.0 released

This release includes a lot of bug fixes and many improvements, including the following:

07/07/11Geomajas @ FOSS4G

FOSS4G is hosted in Denver, Colorado this year and will take place from September 12 to 16.

There will be four Geomajas related workshops at the conference:

06/07/11WMS layer plug-in 1.8.0 released

This release contains some bugfixes, includes additional tests, security improvements and support for the GetFeatureInfo capability.

For the release notes, see

06/07/11Initial release of the REST face

This is the initial release of the plug-in. It currently allows reading layer data in GeoJSON. This can for example be used to display data in alternate clients like OpenLayers.

Future release will included REST/JSON access to the Geomajas commands and write access to the layers.

For the release notes, see


06/07/11Hibernate layer plug-in 1.8.0 released

This release contains various fixes. Most of the code was refactored for stability and speed. Association support is now fully in place. There is support for lazy feature conversion to alow lazy loading.

For the release notes, see

06/07/11OpenStreetMap layer plug-in 1.9.0 released

This is the bugfix release, fixing a problem with CRS transformations.

For the release notes, see

06/07/11Google layer plug-in 1.8.0 released

This release contains bugfixes, simplifies configuration and provides a proper GWT module to allow putting the correct copyright messages on the map in the GWT face.

05/07/11Caching plug-in released

The initial version of the caching plug-in has been released.



This allows improving the speed of Geomajas by caching.


  • Configurable caching strategy.
  • Uses Infinispan as default cache implementation.
  • Automatically invalidates data when needed.

The cached data can be tiles, features, bounds, rasterized data (for the rasterizing plug-in)