|How to easily upgrade an application model (Removing obsolete elements) ?! [message #1713980]
||Mon, 09 November 2015 09:20
Is there any recommendation or best practice how an application model
can be upgraded after plug-ins have been updated?
Let's look at application model fragments that are applied always (not
just initially). Their elements will be applied by replacing the
elements with the same id inside the extended feature. That's ok.
Now if a plug-in developer removes an element in the fragment, no
mechanism exists to remove this element in the persisted application
model. It just stays there forever. So, the developer has to write a
processor which removes the fragment. But this is quite cumbersome
because developers need to be aware of this problem. The same trouble
occur when a developer renames an element id...
Another difficulty is dealing with perspectives. How to update e.g.
perspective name and icons for open perspectives without having to reset
the entire perspective?
Actually, I'd like the application model to keep the persisted states of
parts, part containers, open perspectives and so on. But I also need to
have a proper way to update the application without having users to
delete their application models after an update.
How do you deal with these difficulties?
Thanks for any advice or recommendations!
Powered by FUDForum
. Page generated in 0.01591 seconds