Ticket #74 (accepted Defect)

Opened 13 years ago

Last modified 10 years ago

Cached association definitions are not updated

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


When a child type's URI is changed and then a parent instance is clicked the server crashes with "Topic type xxx not found" where xxx is the old child type's URI.

Change History

comment:1 Changed 13 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 13 years ago by Malte

  • Milestone Release 4.1 deleted

comment:3 Changed 12 years ago by jri

  • Cc dgf, Malte added
  • Complexity changed from 3 to 5
  • Area set to Application Framework / API
  • Module changed from deepamehta-coretypes to deepamehta-core
  • Milestone set to Release 4.1

comment:4 Changed 12 years ago by jri

This problem applies to migrations as well, e.g. when changing a type's URI via setUri().

Once a type's URI is changed *all* direct parent types must be updated automatically (resp. reloaded) and UPDATE_TOPIC_TYPE directives must be send to the Webclient.

Workaround (for migrations):
After changing a type's URI restart the server and only now proceed with the migrations relying on the changed URI.

Last edited 12 years ago by jri (previous) (diff)

comment:5 Changed 11 years ago by jri

  • Milestone changed from Release 4.1 to Release 4.2

comment:6 Changed 10 years ago by jri

  • Milestone Release 4.2 deleted
Note: See TracTickets for help on using tickets.