Release Notes: This beta release includes a binary installer to make life easier, a change from basic authentication to form-based authentication at login, the removal of the reverse proxy as it caused problems with the form-based login, a social network feed which is like a simple a simple Twitter feed, and a simple ISP example as a demonstration of what the platform can do. Centralized versioning of all Jar files was enabled. There were various bugfixes and stabilization changes.
Release Notes: This is the eighth beta, focused on fixing the data source issues that occurred when using MySQL as a data source. Some progress was also made on running the platform on Windows. Windows is still not yet officially supported.
Release Notes: This release corrected problems that prevented Dipforge from running correctly after a fresh install. The installer now sets up the RDF data source correctly. A missing semantics file for the social feed was added.
Release Notes: This beta focussed on stability and added some nice new features. A sleep statement was added to the workflow engine. This supplies the ability to easily implement long running workflow tasks. To demonstrate this, some of the tests were updated. Problems with the Hibernate configuration used by some of the daemons were fixed. This prevents them from consuming all connections on the database and makes sure that the auto commit is not set. Better thread locking was implemented in the event server to prevent dead locking. There were some other minor fixes.
Release Notes: The transaction timeout for internal container based transactions was changed. An if statement in the Leviathan script was changed to correct problems in the workflow engine. Output is now logged to a dipforge.out file. Extra bounds checking was added to transaction persistence. A deadlock in the RDF layer was fixed along with some error messages.
Release Notes: This release fixes the following bugs, adds a keep alive process to the RDF layer to prevent MySQL connections from timing out, adds thread locking support to the RDF layer to prevent dirty reads and writes, and fixes a deadlock in the transaction logic.