Ticket #715 (closed Defect: fixed)

Opened 10 years ago

Last modified 10 years ago

Core API: composite topics loose their label when updated

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.4.1
Component: DeepaMehta Standard Distribution Version: 4.4
Keywords: Cc: dgf, Malte
Complexity: 2 Area: Application Framework / API
Module: deepamehta-core


This is the case when calling update() directly on an object whose child topics are not loaded. In contrast when the update is performed through the Core Service's updateTopic() and updateAssociation() methods the problem does not occur.

Change History

comment:1 Changed 10 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Jörg Richter <jri@…>

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

In 8e357f01b6192895e21ff11879f56f0682d71a14/deepamehta:

Core: fix topic/association label update (#715).

The topic/association's label is properly calculated in case the update() method is called directly on a topic/association while its child topics are not loaded.

Close #715.

comment:3 Changed 10 years ago by Jörg Richter <jri@…>

In 72b9e1db8198207e18301863134d39c516d9d1c4/deepamehta:

Core: refactor update directive (#715).

See #715.

Note: See TracTickets for help on using tickets.