Ticket #402 (closed Defect: fixed)

Opened 8 years ago

Last modified 8 years ago

Revealing a topicmap inside itself throws an error

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.1
Component: DeepaMehta Standard Distribution Version: 4.0.14
Keywords: Cc: dgf, Malte
Complexity: 3 Area:
Module: deepamehta-core

Description

At server-side:

Caused by: java.lang.RuntimeException: Ambiguous getOtherRoleModel() call: both players have ID 7152 in association (association (id=7285, uri="", typeUri="dm4.topicmaps.topic_mapcontext", value="273", composite={},
        topic role (roleTypeUri="dm4.core.default", playerId=7152),
        topic role (roleTypeUri="dm4.topicmaps.topicmap_topic", playerId=7152)))
	at de.deepamehta.core.model.AssociationModel.getOtherRoleModel(AssociationModel.java:98)
	at de.deepamehta.storage.neo4j.Neo4jStorage.buildRelatedTopics(Neo4jStorage.java:571)
	at de.deepamehta.storage.neo4j.Neo4jStorage.fetchTopicRelatedTopics(Neo4jStorage.java:298)
	at de.deepamehta.core.impl.StorageDecorator.fetchTopicRelatedTopics(StorageDecorator.java:185)
	at de.deepamehta.core.impl.AttachedTopic.getRelatedTopics(AttachedTopic.java:156)
	at de.deepamehta.plugins.webservice.WebservicePlugin.getRelatedTopics(WebservicePlugin.java:410)
	... 48 more

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 8 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed

Core: fix delete topicmaps (#402).

Revealing a Topicmap topic inside the topicmap itself works. Deleting the Topicmap topic works.
(was broken with new storage layer.)

BREAKING CHANGES

AssociationModel?: getOtherPlayerId() replaces getOtherRoleModel().

Just the player ID is returned (instad a RoleModel?).
Circular associations are supported (start and end node are the same).

Close ticket 402.

Changeset 0884d52e8f691be42329c93212830c5145cd21be

Note: See TracTickets for help on using tickets.