Changes between Version 2 and Version 3 of Malted/PluginDevelopmentNotes


Ignore:
Timestamp:
27.05.2013 16:25:03 (8 years ago)
Author:
Malte
Comment:

adding rule of thumb for plugins introducing custom-types

Legend:

Unmodified
Added
Removed
Modified
  • Malted/PluginDevelopmentNotes

    v2 v3  
    1818So, especially in a clean installation (DB from scratch) your plugins migration assigning your types to the defualt workspace depends on the "de.deepamehta.workspaces"-plugin which initially creates the "Default Workspace Topic (uri: de.workspaces.deepamehta)". 
    1919 
    20 Adding ''de.deepamehta.workspaces'' into the line "importModels = " of my ''plugin.poperties'' file makes sure that the dm4-workspaces-plugin is started, and thus the default workspace topic is created, before my custom plugin starts running any of its migrations. 
     20Adding ''de.deepamehta.workspaces'' into the line "importModels=" of my ''plugin.poperties'' file makes sure that the dm4-workspaces-plugin is started, and thus the default workspace topic is created, before my custom plugin starts running any of its migrations. 
     21 
     22Addendum: Since the "importModels=" property influences the starting order of all plugins, a rule of thumb was identified in Ticket #465: "If your plugin introduces new types, you have to import the "de.deepamehta.accesscontrol" model". Otherwise ACL-Entries may not be set correct during installation of your plugin since the ACL-Plugin is not there to do it's job.  
    2123 
    2224