| 3 | == DeepaMehta 4.0.1, 2011-07-29 == |
| 4 | |
| 5 | 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. |
| 6 | |
| 7 | Affected are the following association semantics: |
| 8 | - Core: data type assignment of a topic/association type |
| 9 | - Core: index mode assignment of a topic/association type |
| 10 | - Topicmaps: topic/association assignments of a topicmap |
| 11 | - Workspaces: topic/type assignments of a workspace |
| 12 | |
| 13 | CAUTION when editing such an association that was created with 4.0: |
| 14 | In this situation you must set role type "Default" manually for the correct association end. |
| 15 | Otherwise the respective association gets corrupted. |
| 16 | |
| 17 | For associations newly created in 4.0.1 there is no issue. |
| 18 | |
| 19 | These 3rd party components are updated in 4.0.1: |
| 20 | - Jersey 1.5 -> 1.8 |
| 21 | - Jettison 1.2 -> 1.3 |
| 22 | - Neo4j Mehtagraph 0.7 -> 0.8 |
15 | | - new type editor. All values are represented as reusable semantics-attached topics. |
16 | | - new topic type "Resource" to collect web resources |
17 | | - new icons |
18 | | - bug fix in topicmap handling (when you have multiple topicmaps open) |
19 | | - cleaner display, less clutter |
| 35 | - new type editor. All values are represented as reusable semantics-attached topics. |
| 36 | - new topic type "Resource" to collect web resources |
| 37 | - new icons |
| 38 | - bug fix in topicmap handling (when you have multiple topicmaps open) |
| 39 | - cleaner display, less clutter |