Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on Oct 20, 2011
  1. 4.0.5 Release.

    Update version numbers and README.
  2. Help module: add 2 contributors to the about box.

    ... Silke Meyer and Rolf Kutz
Commits on Oct 18, 2011
Commits on Oct 16, 2011
  1. New webclient feature: Permalinks (#106).

    Individual topicmaps/topics can be addressed via webclient URLs.
    To jump into a particular topicmap:
    To jump into a particular topicmap and display a particular topic of that map:
    Browser compatibility: the permalinks work in all browsers. However, to see the address bar's location change *while you navigate* (and for functional back and forward browser buttons) Firefox 4, Safari 5, or Chrome is required.
    Note: the "topicmap" URL query parameter is not supported anymore. Use the new URL format instead.
    Close ticket 106.
Commits on Oct 15, 2011
  1. Files module: fix Windows file drag'n'drop (#91).

    Note: draging'n'dropping files from arbitrary locations (in particular different Windows drives) collides with the concept of a single-rooted file repository (as realized by the proxy module). For the moment on Windows drag'n'drop operations are only supported from the C: drive (actually the drive DM is started from).
    See ticket 91.
Commits on Oct 14, 2011
  1. Proxy module: fix Windows path problem (#91).

    All file related features should now work properly on Windows too.
    See ticket 91.
Commits on Oct 5, 2011
  1. Wrapping up the Apache reverse proxy fix (#107).

    The original problem was that DM's file related features didn't work if and
    only if DM was running behind an Apache reverse proxy.
    What we've learned:
    1) Apache decodes URLs before passing the request to the backend application!
       As a consequence Jersey's default pattern for matching the request's path
       segments ([^/]+?) does *not* match if the URL contains encoded slashes
       (e.g. when a path is encoded *within* a path segment). This caused Jersey
       to respond with 404.
       The solution was to use a custom pattern (.+) for Jersey.
    2) By default Apache doesn't allow encoded slashes in URLs at all! Such URLs
       are refused with a 404.
       The solution was to modify this behavoir by the means of Apache's
       AllowEncodedSlashes directive.
    Thanks to JuergenN and Silke for helping to track things down!
    Close ticket 107.
  2. Files module: address a 404 issue (#107).

    Change regex for the other requests as well.
    See ticket 107.
  3. Files module: address a 404 issue, 3rd try (#107).

    3rd try to fix a 404 issue in conjunction with a reverse proxy setup.
    Change regex for POST /files/folder requests.
    See ticket 107.
  4. Proxy module: address a 404 issue, 2nd try (#107).

    2nd try to fix a 404 issue in conjunction with a reverse proxy setup.
    Now we flush the response stream.
    See ticket 107.
  5. Topicmaps module: fix background images (#103).

    No forced map refresh is required to see the background image.
    (For newly assigned background images a client reload is still required)
    See ticket 103.
  6. Topicmaps can have a background image (#103).

    To set a background image for a topicmap:
    1) Reveal the Topicmap topic (e.g. via the "Associations" listing).
    2) Create a File topic corresponding to the image file (either via file browser or via drag'n'drop).
    3) Associate the topicmap with the file.
    4) Retype the association to "Aggregation". Make the topicmap the "Whole" and the file the "Part".
    To choose another background image for a topicmap:
    1) Proceed as described above.
    2) Reactivate the previous background image (e.g. by retyping the association to "Association").
    That's it basically. However, for the moment there are a lot of issues:
    - To actually see the map background you have to reload the client (http://localhost:8080/)
    - The background appears only after a forced map refreshing (e.g. by moving it a little)
    - IMPORTANT: there must be only *one* background image per map. Otherwise the map gets corrupted.
      So, the "Reactivate" step (2) above is crucial.
    See ticket 103.
  7. Topicmaps module: extend topicmap serial format

    The Topicmap topic itself (including its composite value) is contained in the "info" property.
    In preparation to "Maps with background image" (#103).
Commits on Oct 4, 2011
  1. Webclient: more flexible page and form rendering.

    Complex child types can be made non-viewable and/or non-editable via view configuration settings.
    In preparation to "Maps with background image" (#103).
Commits on Oct 3, 2011
  1. Proxy module: address a 404 issue (#107).

    1st try to fix a 404 issue in conjunction with a reverse proxy setup.
    See ticket 107.
Commits on Oct 2, 2011
  1. Webclient: browser's back buttón works (#106).

    The browser's back/forward buttons steps through the history of selected topics and topicmaps.
    Each topic/topicmap has a unique URL which appears in the browser's address bar.
    Firefox 4, Safari 5, or Chrome is required.
    Basically it works. A lot of issues remain, e.g.
    - when topics are deleted history gets corrupted
    - selected associations are not included in the history
    - when stepping back beyond the history begin an error occurs
    - the displayed URL does not actually work yet (permalink feature)
    For developers there are 3 new webclient hooks:
    - pre_push_history()
    - pre_pop_history()
    - post_reset_selection()
    See ticket 106.
Commits on Oct 1, 2011
  1. Webservice module: fix package name.

    Update version numbers to 4.0.5-SNAPSHOT
Commits on Sep 27, 2011
  1. 4.0.4 Release.

    Update version numbers and README.
Commits on Sep 24, 2011
  1. README has a .txt extension in binary release #88

    Close ticket 88.
  2. Webclient/Core: label configurations work #41

    Topic label rules can be configured interactively.
    A label rule is bound to a topic type.
    Subject to label rules are *complex types*.
    (Simple types need no rule: the topic's value IS its label.)
    To edit the label rule:
    1) Reveal a complex topic type.
    2) Press "Edit". You see the topic type's immediate child types displayed as boxes.
    3) To choose which child types to include in the label select the respective "Include in Label" checkboxes.
    4) Bring the child types in the desired order by vertically moving the boxes.
    5) Press "Save".
    - Once a label rule is changed the existing topic instances are *not* adjusted. To apply the new rule select the topic, press "Edit" and then "Save". Applying a changed rule to *all* existing topic instances might be a future feature.
    - There is only *one* child type sequence: the order by which the child types are rendered in the content panel is the same order that is used to construct the label. Maintaining 2 individual sequences (content panel rendering vs. label construction) might be a future feature.
    - Label rules are cascading. The "Person" type e.g. is configured to use the "Person Name" type as the label. The Person Name type in turn is configured to use "First Name" AND "Last Name" as the label. So, consider all hierarchy levels when defining a label rule.
    - If there is no label rule defined (that is all "Include in Label" checkboxes are deselected) the former default rule applies: use the first simple type found by a depth-first traversal.
    See ticket 41.
Commits on Sep 23, 2011
  1. Webclient fix: edit view configurations

    Commit [77a834d] (1 week ago) broke the view configuration edit mechanism and made topics unvieable.
    This is fixed.
Commits on Sep 22, 2011
  1. Core/Type Editor: change child type order (#77).

    On the edit page for a composite type:
    drag'n'drop the child type boxes in the desired order and press "Save".
    The other 2 functions are still missing.
    See ticket 77.
Commits on Sep 21, 2011
  1. Core: declarative label configurations work (#41).

    Try the Contact's module Person topic type.
    Still missing: interactive label configuration.
    See ticket 41.
  2. Core: more on feature "Label Configuration" #41.

    Not yet functional.
    See ticket 41.
Commits on Sep 19, 2011
  1. Core: begin of feature "Label Configuration" #41.

    Data model: extend association types "Composition Definition" and "Aggregation Definition" by a boolean "Include in Label" child type.
    See ticket 41.
Commits on Sep 17, 2011
  1. Core: tweak limited search result labels (#98).

    See ticket 98.
  2. Core: limit search results (#98).

    Now functional.
    Search result limit is set to 100 items.
    See ticket 98.
Commits on Sep 16, 2011
  1. Core: limit search results (#98).

    Extend Core API by "maxResultSize" argument.
    Not yet functional.
    See ticket 98.
  2. Webclient fix: search results are sorted (#69).

    Close ticket 69.
  3. Files module fix: remove "Edit" button (#93).

    File and folder topics are not editable.
    You must reset your DB.
    Furthermore in webclient module: refactor view configuration default value mechanism.
    Close ticket 93.
Commits on Sep 14, 2011
  1. Files module fix: audio player is not cropped (#90).

    See ticket 90.
  2. Proxy module: support for IPv6 (#92).

    It should work now.
    If you want restrict proxy access to localhost you should change the `` setting in `./pom.xml` to `::1/128`.
    See ticket 92.
Commits on Sep 12, 2011
  1. Runtime: DM server runs in background (#46).

    - Drop Gogo shell bundles from distribution.
    - Export package `org.osgi.service.log` (it is needed by Jetty and was formerly exported by Gogo).
    End users: stop DM by Ctrl-C.
    Server: stop DM by killing via PID.
    See ticket 46.
Commits on Sep 11, 2011
  1. Proxy: fix REST API call getResourceInfo() (#90).

    The `dm4.proxy.files.path` setting is respected.
    See ticket 90.
  2. Files/Proxy modules: handle and report NOT FOUND.

    404 NOT FOUND happens e.g. if the server is restarted with a different `dm4.proxy.files.path` setting.
    File and folder topics retrieved before are not valid anymore. A `404 (Not Found)` message is displayed for them.
    See ticket 90.
Something went wrong with that request. Please try again.