Introduction

Already present

The first and foremost requirement is that the project is ISO-functional and ISO-compatible with geoweb-eaasy v1. To this end, automated migration procedures have been developed to ensure the installation of geoweb-easy v1 with a database of existing geoweb-easy data. These migration procedures will be explained in the section on the server.

Technological choices

Unlike geoweb-easy v1, geoweb-easy v2 will integrate a full JavaScript engine on the client side. If we take the five parts of the project:

  1. The widgets part will be based on the last version of YUI: 3.5.1
  2. The Java part is based on Java 5 and will use the Sax libraries for managing widgets
  3. The database part uses the current version of Hibernate used as Standard in geoweb, that is
Hibernate 3.2
  1. The Dispatcher part of the URL is based on Spring MVC 25
  2. The REST Web Services part is based on Apache CXF, and notably uses the Web plugins manager
Services de Geoweb.
The Jackson 1.8.5 library handles client-server mapping and the project will integrate cityportal-jar for managing the POI.