Community
Participate
Working Groups
Currently in DSF there is no mechanism to store persistent settings in a debug session. The existing features which require this use other means to store these settings, such as the ILaunch object or IPresentationContext. It would be ideal if there was a service which abstracted the persistence mechanism. This interface would need to perform two main tasks: 1) Provide a mechanism for persisting data model contexts and comparing contexts to ones that were persisted. 2) Provide mechanism to save and read persistent settings for a given data model context.
I'm not sure if this is related, but in CDI there are a bunch of user (instance specific, I would say) attributes which find their way into the launch xml. For example: which global variables the user has chosen to be visible. The launch xml seems the wrong place for this as in many cases they end up in version control.
I think it is somewhat related. Since filing this bug, I've been thinking about different needs for persistent storage. One area is the display settings, which as you point out should really be saved with the view. The other is configuration information, such as source lookup paths. This proposed service is to create a DSF abstraction for the configuration information storage, which in most cases would be backed by the launch configuration.
