Ticket #555 (closed Enhancement: fixed)
Extend server-side Topicmaps API
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1.3 |
Component: | DeepaMehta Standard Distribution | Version: | 4.1.2 |
Keywords: | Cc: | dgf, Malte | |
Complexity: | 3 | Area: | Application Framework / API |
Module: | deepamehta-topicmaps |
Description
- TopicmapViewmodel? should have 2 public methods:
- getTopics() which returns an Iterable<TopicViewmodel?>
- getAssociations() accordingly
- TopicmapsService? should get a new method:
- boolean isTopicInTopicmap(topicId, topicmapId)
- TopicmapsService? could provide a convenience method (not necessarily RESTful):
- void addTopicToTopicmap(long topicmapId, long topicId, int x, int y, boolean visibility)
Currently, when used at server-side the caller must perform:
addTopicToTopicmap(topicmapId, topicId, new CompositeValueModel() .put("dm4.topicmaps.x", x) .put("dm4.topicmaps.y", y) .put("dm4.topicmaps.visibility", true)
Thank you, Malte, for bringing up this issues!
Change History
comment:2 Changed 11 years ago by Jörg Richter
Extend server-side Topicmaps API (#544).
CHANGES
- TopicmapViewmodel has 2 new methods:
- getTopics() returns an Iterable<TopicViewmodel>
- getAssociations() returns an Iterable<AssociationViewmodel>
- TopicmapsService has a new method (not RESTful):
- boolean isTopicInTopicmap(long topicmapId, long topicId)
- TopicmapsService has a new convenience method (not RESTful):
- void addTopicToTopicmap(long topicmapId, long topicId, int x, int y, boolean visibility)
- mew package/classes:
- de.deepamehta.plugins.topicmaps.model.TopicViewmodel
- de.deepamehta.plugins.topicmaps.model.AssociationViewmodel
BREAKING CHANGES
- TopicmapViewmodel moved package:
de.deepamehta.plugins.topicmaps.TopicmapViewmodel
-->
de.deepamehta.plugins.topicmaps.model.TopicmapViewmodel
See #555.
Note: See
TracTickets for help on using
tickets.