Mercurial > dive4elements > framework
view Changes @ 89:d348fe1fd822
More javadoc (fixes small glitches, too).
artifacts/trunk@845 c6561f87-3c4e-4783-a992-168aeb5c3f6f
author | Sascha L. Teichmann <sascha.teichmann@intevation.de> |
---|---|
date | Fri, 26 Mar 2010 16:16:32 +0000 |
parents | 66f43d1e69eb |
children | f03a309a037f |
line wrap: on
line source
2010-01-27 RELEASE 0.4 New: * Extended XML helper utilities a bit more * Added a new interface describing services via XML documents via /services 2009-12-17 RELEASE 0.3 New: * Extended XML helper utilities a bit * Added a new general proxy artifact. FIXED: * issue106: Konfiguration der GNV-Chart-Templates gehört nicht in das Artefakt-Framework 2009-11-13 RELEASE 0.2 New: * Configuration documents can be made relativ to ${artifacts.config.dir} * Splitting up configuration of artifacts in depence to the product. * Added a first HOWTO for setting up the environemt and the artifact server 2009-10-07 RELEASE 0.1 New: * Two sub projects: 'artifacts' and 'artifact-database' - 'artifacts' is a set of generic interfaces modelling the workflow to parameterize a process and producing outputs. An artifact is created via factories. It describes itself via 'describe', it is parameterized via 'feed' and brought to new states with 'advance'. Once able to produce output 'out' returns the requested product. - 'artifact-database' is the default implemention of the workflow described with 'artifact'. * artifact-database persists artifacts with a H2-database [http://www.h2database.com] (default) or a PostgeSQL 8.3+ database [http://www.postgresql.org/] (optional) * artifacts may spawn background threads to copy with long running processes. After finishing work they are able to re-synchronize themselves to the artifact database. * artifact-database is accessible via an HTTP REST server implemented on top of the Restlet API http://www.restlet.org/ It has to be started as a service. Default TCP port: 8181 HTTP GET '/factories' returns list of available factories. HTTP GET '/create' creates new artifact. HTTP GET '/artifact/{uuid}' returns a description of an artifact. HTTP POST '/artifact/{uuid}' modifies an artifact ('feed', 'advance') HTTP POST '/artifact/{uuid}/{out}' delivers output for an artifact. * artifact-database is configured with as XML file named conf.xml (default placement in directory $HOME/.artitactdb, directory may be changed with system property "artifact.database.dir")