deegree2 developer information
Start page of the deegree2 development and design documentation.
Contents
1. General
deegree2 is available in a stable version which can be used in productive systems.
For an overview on the implemented services for deegree2 please refer to the main deegree2 page.
If you are looking for documentation or tutorials you should go to the deegree2/users page.
If you are interested in the available deegree products, please check the ProductInformation page.
2. Requirements
If you want to be an official developer for deegree, please have a look at the deegreeCommitterGuidelines, the StructuresAndProcedures and the deegree developer guide.
3. Services
Currently there is no developer specific documentation for deegree2 services.
Please have a look at the services documentation in the SVN. And please also check the deegree2/users documentation.
To test WebServices for OGC compliance, see the TeamEngine and the ServiceTesting pages for more information.
Read more about CommonProblems when setting up deegree WebServices.
4. Clients
For a short walkthrough on how to develop a module for iGeoDesktop see HowToWriteNewModulesForIGeoDesktop.
Currently no other developer specific documentation for deegree2 clients is available. Please have a look at the clients documentation in the SVN. And please also check the deegree2/users documentation.
5. API subsystems
The ApiSubsystems page describes the software modules which the deegree framework consists of, and which provide the functionality that the clients and services use internally.
6. Build process and SVN
See the page on Eclipse for deegree specific settings and check the subpage Eclipse/DeegreeSVN for checking out the deegree SVN from Eclipse.
If you are a developer with the right to commit to the svn directly, you are required to use the Eclipse/CommitTemplates. Best to integrate them into your Eclipse. And please, don't forget to read and follow the deegree developer guide.
There is also a description on Deployment of deegree2 with ant, and a deegreeCompatibility list available.
7. Miscellaneous
Different deegree2 components (services, clients) need different external libraries. Therefore we established an overview over which ExternalLibraries are used by which deegree2 application. Check this page to make sure you have every lib you need.
some details on DataStore and SQL
other stuff: OWSCommon, DataModel, InputOutput
8. Coding practices
Have a look at the DevelopersCorner
Check out the XmlFragments
9. deegree2 package structure
org.deegree |
package content |
crs |
deegree's (low-level) CRS and transformation implementation. Here your find classes for handling CRSs and their transformations. If you need a special CRS or transformation you have to implement/extend interfaces/classes defined here. |
datatypes |
special datatypes that are not exclusive for geoprocessing; most important is Types and QualifiedName |
enterprise |
classes for web communication; as well for OGC service implementations as for iGeoPortal |
framework |
This package contains several packages/classes that do are not directly related to geoprocessing and OGC. Here you find tools for reading/writing images; deegree's logging framework or classes for handling current processes, etc. |
graphics |
everything required to render geospatial data to a map (incl. OGC SLD implementation). |
i18n |
central messaging classes/properties. To enable multi language support (e.g. for exception messages) strings are defined here. They can be accessed using class org.deegree.i18n.Messages |
io |
Here you find classes for reading/writing data from/to supported file formats and databases. Very important is io.datastore package where deegree's OR-mapping (used by WFS) is located. Read more on InputOutput |
model |
deegree's data model -> geometries, features, coverages ... Read more on the DataModel |
ogcbase |
- |
ogcwebservices |
Here you find all WebServices implemented in deegree. The name of the module is not absolutely correct because two of the services (wass and wmps) are not based on OGC specifications. |
owscommon |
OWS commons implementation. Since there are several versions of OWS commons specfication implemented in differen OGC web services. This is a not so nice package. More details in OWSCommon. |
portal |
especially handler/listener classes for iGeoPortal standard and portlet edition. Most of the functionality of both portals can be find here. |
processing |
here you find classes for processing raster data; e.g. converter classes or interpolation algorithm. |
security |
Includes a) deegree's User and Rights Management and b) owsProxy that can be used to protect OGC web services for unauthorized access. See iGeoSecurity for more details. |
tools |
a loosley collection of command line applications that simplify working with deegree or offer some useful functionalities. E.g. creating WFS configuration from a shapefile or a database table, transforming GML into a shapefile, transforming shapes or rasterfiles from one CRS into another... See deegreeTools for more details. |