A first look at deegree2

Background

In spring 2003 the consortium of lat/lon, geotools and geoserver was assigned by the OGC to realize the reference implementations for OGC WFS 1.0.0 and WMS 1.1.1 specifications. While the WFS has been realized in the context of geoserver the WMS reference implementation became part of the deegree project. Six month later the OGC planned to realize reference implementations for WCS 1.0.0 and CS-W 2.0 specifications in the context of OWS2 . The realization of both reference implementations was assigned to lat/lon. As a result both OWS services are incorporated into the deegree framework..

In addition to the growing need for some basic changes, the integration of a client API and the aim to harmonize several parts of deegree with the GeoAPIproject was the starting point for a new major release of deegree. [The GeoAPI project was founded by geotools, geoserver and lat/lon during the realization of the first reference implementations in 2003.] Our first plan in winter 2003/2004 was to redesign the WFS API of deegree first and then to start the redesing of the other APIs step by step. After some tests and design concepts for the new WFS we unfortunately had to skip this plan because of the limited time we had to realize WCS and CS-W reference implementations.

What we have planned and what we did

In spring 2004 we started to redesign deegree API using following coarse guide line:

• simplifying the API by removing unnecessary interfaces
• simplifying the package structure remove the org.deegree_impl branch
• unifying API (access and configuration) of OWS realized in deegree
• simplifying web interface by using one central servlet and proxy pattern for all OWS instead of one servlet for each OWS
• adding direct API access to the OWS operations beside event-based access
• more logical and consitent package structure
• substitution of deegree specific Debug (logging) object by established logging APIs
• redesign of multi-threaded parts of deegree by moving handling of threaded processing to a specialized class
• a better ant support for developers
• substitution of deegree classes for pooling and caching by established open source projects (jakarta commons and EHCache)
• substitution of the deegree database access layer by incorporating the hibernate persistence service

Not all of this has been finished yet. Especially the redesign of the WFS including the substitution of deegree database access by hibernate won't be finished before end of the year. Nevertheless at the upcoming end of OWS2 the API of deegree is elaborated so far that we like to offer a first look to the community.

So here you can download the java doc and the current sources to have a look at the new API. The code base now contains several XML and XSLT documents that are assigned to specific classes and will be loaded by the classloader. Also available are scripts that can be used to compile and deploy deegree. Last but not least an example of WCS, WFS and CS-W are put together in a war-archive to be easyly deployed in a web server (you must add data for the services by your own).

CVS access

bundled download

Please read the read me file in deegree src zip file for further information.

deegree2 alpha-2.1 release:

deegree2 beta-1 release: