Ticket #766 (closed Defect: fixed)

Opened 6 years ago

Last modified 6 years ago

Core: objects loose label when updating child topics

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

Description

A topic/association looses its label if set() or setRef() is called on its ChildTopics object at a time when both conditions are met:

  • The set child topic is not the one used for labeling
  • The topic/association's child topics are not loaded (in particular the one(s) involved in labeling)

This bug was introduced with DM 4.4 in conjunction with on-demand child topic loading.

Change History

comment:1 Changed 6 years ago by jri

  • Status changed from new to accepted

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

In cda185daa40ce1eb2c36d8b5f77dfa81bdd1971c/deepamehta:

Add test to illustrate the lost-label issue.

See #766.

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

In b9e905d127134ac36c782246f6738c2a23575237/deepamehta:

Core fix: keep label when updating childs (#766).

When calling set() or setRef() on a ChildTopics object the topic/association's label remain intact resp. is properly recalculated in any case.

See #766.

comment:4 Changed 6 years ago by Jörg Richter <jri@…>

In 4d49220d40ff9549d8c7ebe930d590607195beb5/deepamehta:

Update lost-label test (#766).

Now the test passes.

See #766.

comment:5 Changed 6 years ago by Jörg Richter <jri@…>

In 470291a96fea00c1d6e4e61f7eeb3eb42967dd4f/deepamehta:

Add test: Java's missing multiple dispatch (#766).

See #766.

comment:6 Changed 6 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.