Hi Bob
For me the main issue was usability issue which was there in bpel.xxx.xxx.noEmbeddedEditors implementations. Where there is no content assist support, and users/developers complaining it is hard to hand write a complex expressions. I know that you took this noEmbeddedEditors approach due to eclipse platform api changes. It seems like the fix for the bug 46207 solves the embedded editors problem. I think we can go back to the earlier implementation again once that issue was fixed WDYT.
The fix that i have provided is a simple one which enables the Content-assist and variable picker on the noEmbeddedEditors implementation. I'm sorry that i don't have experience in Xtext stuff therefore i don't know what are the pros and cons of moving to that approach. If existing XPath parser works fine what about just use it as it is and fix the embedded editors issue once 46207 is fixed. Or can we improve my fix and continue this noEmbeddedEditors approach to support all the languages without embedded editors (i.e based on StyledText and textviewer etc).
Thanks
Susinda