DeepaMehta 5

[jri]

The DeepaMehta 5 highlight features are addressed in separate tickets:

• Rewritten Webclient (#1073)
• Identity/Value data model (#1089)

This ticket collects commits/discussions about general DM5 topics.

[Jörg Richter <jri@…>]

In 3de734fccf0ab77a2b66cac109127f282bae1256/deepamehta:

Adapt test environment to DM5 (#1080)

See #1080

[Jörg Richter <jri@…>]

In 8a641558d1a45e464112ee6158c95f378481600f/deepamehta:

Adapt production build system to DM5 (#1080)

See #1080

[Jörg Richter <jri@…>]

In 846f15c44d7bf873a10036d466fb08078669e57a/deepamehta:

Fix config for webpack-dev-server 2.5.0 (#1080)

​https://github.com/webpack/webpack-dev-server/issues/960

See #1080

[Jörg Richter <jri@…>]

In 487169330308c0442529072627cef8646ddd7378/deepamehta:

Fix OSGi exports for running headless (#1080)

See #1080

[Jörg Richter <jri@…>]

In e388261add2ffd204d4af1cb0c7046c6df27481f/deepamehta:

Refactor JAX-RS resource registration (#1080)

Use one central /api resource that dispatches via sub resource locator.
JAX-RS injection no longer work.
Discontinued.

See #1080

[Jörg Richter <jri@…>]

In 90043da89147200a883b795a68b88174c9a02198/deepamehta:

Topicmaps API: addRelatedTopicToTopicmap() (#1080)

See #1080

[Jörg Richter <jri@…>]

In 791c7996910b2dba9b327f566f3dc3f0fe4ff242/deepamehta:

REST API: create-workspace uses query params (#1080)

BREAKING CHANGE

The create-workspace request changed:
`
POST /workspace?name=...&uri=...&sharing_mode_uri=...
`

Instead of path params query params are used now.
uri is optional.

Background: the proxy of the webpack-dev-server accidentally converts double slashes, as caused
by empty path segments, into single slash, resulting in a changed (= corrupted) URL semantics.
​https://github.com/webpack/webpack-dev-server/issues/880

See #1080

[Jörg Richter <jri@…>]

In d12d3b318c46d3201993048d9378197ff7b199a0/deepamehta:

WebSockets? service: send messages in background (#1080)

See #1080

[Jörg Richter <jri@…>]

In 87cad11e6712d6eb7bc646456ed6516eb3cd60ea/deepamehta:

WebSockets?: terminate send messages thread (#1080)

See #1080

[jri]

In 9a1f024dfc0bb22107645b4c857dfe5752cb82d2/deepamehta:

Revise session management (#1080)

In DM4 a HTTP session is created only when a user loggs in.
On logout the session is invalidated.

In DM5 a session is created for every user, regardless if logged in or not.
On logout the session is *not* invalidated.
The logg-state is represented by the existence/absence of the "username" session attribute.

This way DM5's handling of WebSocket? connections is more straight forward.
Now a WebSocket? connection is *always* associatied with a valid HTTP session.
Note that the DM5 Webclient creates a WebSocket? connection at launch time, when no user might logged in.

See #1080

[jri]

In d3efa755335b344c62255125b9b1b6fdde6eb497/deepamehta:

Topicmaps Service: also assocs have view props (#1080)

Topicmaps API:

void addAssociationToTopicmap(long topicmapId, long assocId, ViewProperties viewProps)

void setViewProperties(long topicmapId, long topicId, ViewProperties viewProps)
->
void setTopicViewProperties(long topicmapId, long topicId, ViewProperties viewProps)
void setAssociationViewProperties(long topicmapId, long assocId, ViewProperties viewProps)

See #1080

[jri]

In 734dc5a0b3ed81aaa3e394eed467c2c16252a497/deepamehta:

Storage: index HTML as is (#1080)

HTML tags are not stripped before indexing.
Indexing the exact value is required by DM5's value updater.

See #1080

[jri]

In 77ce3510f5df4f4b1774903159c1b2ac79c5b8d8/deepamehta:

Webservice: add delete-multi resource methods (#1080)

DELETE /core/topics/{topicIds}
DELETE /core/assocs/{assocIds}
DELETE /core/topics/{topicIds}/assocs/{assocIds}

{...Ids} are comma separated ID lists, non-empty.

See #1080

[jri]

In c92f84e1c972237e1dc6171f40c6fce97264b4ba/deepamehta:

Core: child topics are not deleted (#1080)

See #1080