I've been using XAM/XDM extensively in maven support since 6.5. It works great apart from some issue I'd like to
summarize here.

1. ModelSource get cached internally but I always have to recreate tem as the cache is not generally available. As a
consequence you cannot have both editable and non-editable ModelSource for one physical file. I've got hit by this when
I used a non-editable in navigator (which by nature doesn't edit anything), but then later in the game got errors from a
Model+ModelSource which I created to be editable. Unfortunately the cached non-editable one was used.

2. Transactions are hard to work with, rollback appears not to be working 100% for complicated stuff (it somehow breaks
the model and on new occasion the model breaks).. undo/redo seems to scare people when they see the entire document
disappear and then reappear the old version..

3. sync() and refresh(). never really understood what sync does. Is it syncing from the model to the document? I figured
I need to do a sync() *before* starting a transaction or doing any work with the model. how is that better than
refresh() (which it might call as well in the end)?
refresh() when called explicitly or implicitly by other calls inside the xam/xdm framework seems to invalidate all the
models other parts of the IDE are holding or even processing, that's rather unfortunate and source of many errors.
Together with a fact mentioned in point 1 it means the access to any interaction with the model shall be guarded by a
Write Mutex, so that threads don't step on each other toes and after each job the model shall be thrown away and
recreated via refresh(). Unfurtunately it's not the case.

related issues #165465, #166414 and possibly #168281