Version 2 (modified by JuergeN, 12 years ago) (diff)


DeepaMehta 4.0.1, 2011-07-29

In DeepaMehta 4.0.1 the data model has slightly changed: Topic types are never used as role types anymore. Instead the new role type "Default" is used. The existing 4.0 type definitions in the DB are not migrated. However, the 4.0.1 application code is compatible with the 4.0 model.

Affected are the following association semantics:

  • Core: data type assignment of a topic/association type
  • Core: index mode assignment of a topic/association type
  • Topicmaps: topic/association assignments of a topicmap
  • Workspaces: topic/type assignments of a workspace

CAUTION when editing such an association that was created with 4.0: In this situation you must set role type "Default" manually for the correct association end. Otherwise the respective association gets corrupted.

For associations newly created in 4.0.1 there is no issue.

These 3rd party components are updated in 4.0.1:

  • Jersey 1.5 -> 1.8
  • Jettison 1.2 -> 1.3
  • Neo4j Mehtagraph 0.7 -> 0.8

DeepaMehta 4.0 RC1, 2011-07-20

Today the 1st release candidate of DeepaMehta 4.0 has been released.

This is the first release with the all-new property-less data model as recently described:>

The version planned as "DeepaMehta 3 v0.5" now become "DeepaMehta 4.0". From now on DeepaMehta's version numbers follow the classic *major*.*minor*.*bugfix* schema.

Improvements for users:

  • new type editor. All values are represented as reusable semantics-attached topics.
  • new topic type "Resource" to collect web resources
  • new icons
  • bug fix in topicmap handling (when you have multiple topicmaps open)
  • cleaner display, less clutter

The cleaner display is because not all the plugins (workspaces, time, access control, ...) are adapted to the new data model so far. So, for the moment there is not so much meta data displayed (timestamps, workspaces assignments, creator, modifier, ...).

Improvement for developers:

  • New core service API. All the domain objects (Topic, Association, ...) are attached to the database. So, the developer must not care about DB-updates.
  • Domain models (type definitions) provided by a plugin can be build upon the domain models provided by other plugins. The dependencies are handled by the framework.

Download the release: Start as usual via the provided startscripts.

Build from Source:

For further information see the README (scroll down):

Troubleshooting: If the browser shows 404 while this exception appears in the terminal ...

com.sun.jersey.api.container.ContainerException?: No WebApplication? provider is present

... then refresh the HTTP Jetty Bundle by typing "refresh 1" in the terminal (checkout the proper bundle ID before by using the "lb" command).

Thanks go to Jürgen and Danny who helped to organize this release.

Cheers, Jörg