grammar org.eclipse.xtext.example.fowlerdsl.Statemachine with org.eclipse.xtext.common.Terminals

generate statemachine "http://www.eclipse.org/xtext/example/fowlerdsl/Statemachine"

Statemachine :
    'Statemachine' name = QualifiedName '{'
	('commands' 
		commands+=Command+ 
	'end')?
	states+=State*
	'}'
;

Command:
	name=QualifiedName code=ID
;

State:
	'state' name=QualifiedName
		('actions' '{' actions+=[Command|QualifiedName]+ '}')?
	'end'
;

QualifiedName:
  ID ('.' ID)*
;

// old scoping and exporting API
// fragment = scoping.ImportURIScopingFragment auto-inject {}
// fragment = exporting.SimpleNamesFragment auto-inject {}
    
// scoping and exporting API
fragment = scoping.ImportNamespacesScopingFragment auto-inject {}
fragment = exporting.QualifiedNamesFragment auto-inject {}
fragment = builder.BuilderIntegrationFragment auto-inject {}

Statemachine Main {
	commands 
		clearAlarm alarm1
	end		

	state state1
	actions {
		Commands.soundAlarm
		clearAlarm
	}
	end
}

Statemachine Commands { 
	commands 
		soundAlarm alarm1
	
	end 
}

java.lang.RuntimeException: No EObjectDescription could be found in Scope State.actions for Statemachine'Commands'.commands[1]->Command'clearAlarm'
Semantic Object: Statemachine'Main'.states[0]->State'state1'
URI: platform:/resource/tst/main.statemachine

1. Open main.statemachine with sample reflective Ecore model editor
   
2. Load commands.statemachine (using menu Load Resource ...) to add commands.statemachine resource to the ResourceSet.
   
3. Select clearAlarm Command from main.statemachine resource and drag it to the Statemachine Commands model element in the commands.statemachine resource.
   
4. Save the resources
   

1. When the containment of the clearAlarm Command element changes from the Main statemachine to Commands statemachine, it's fully qualified name should become Commands.clearAlarm. So instead of searching the global scope for a Command element with name clearAlarm, it should search for a Command element with name Commands.clearAlarm. If so, how to correct for this behavior?
   
2. The clearAlarm Command element is searched for in the incorrect scope. When debugging the code, I noticed that the element is searched for in the local scope as well as the parent scopes. It could be that the chain of scopes is incorrect, but I failed to discover any problem here. Also, I would expect the global scope to contain the element anyhow, since it's moved to a different resource. If the scopes are incorrect, how to fix this?
   
3. It's the Xtext Builder's responsibility to update the global scope corresponding to the move of the clearAlarm Command element to the commands.statemachine resource. Could it be the case that the update hasn't been finished yet when the cross-reference to this element is serialized to disk? If so, how to correct for this?
   
4. ...?
   

• Eclipse Modeling Tools 4.5.2.20160218-0600
  
• Xtext Complete SDK 2.9.1.v201512180746
  

To avoid outdated scopes after programmatically changing the model, you'll need to enable "live scoping" via org.eclipse.xtext.ui.resource.LiveScopeResourceSetInitializer. See JavaDoc for an explanation.

1. The RuntimeModule contains the following snippet.
   

   	// contributed by org.eclipse.xtext.generator.builder.BuilderIntegrationFragment
   	public void configureIResourceDescriptionsPersisted(com.google.inject.Binder binder) {
   		binder.bind(org.eclipse.xtext.resource.IResourceDescriptions.class).annotatedWith(com.google.inject.name.Names.named(org.eclipse.xtext.resource.impl.ResourceDescriptionsProvider.PERSISTED_DESCRIPTIONS)).to(org.eclipse.xtext.resource.impl.ResourceSetBasedResourceDescriptions.class);
   	}
   

   
   The PERSISTED_DESCRIPTIONS key is apparently the default fro the ResourceDescriptionsProvider injected. I would have expected that in this case, the Xtext index would only be updated when the resources are modified, also in case of using the Xtext generated textual editors. However, when opening multiple Xtext resources, I see that the index is updated 'live'. I conclude this as the content assist is updated and cross-references are resolved correctly, even without saving the resources. My question therefore is what is the effect when injecting the ResourceDescriptionsProvider instance with the key set to LIVE_SCOPE?
   
2. Is it possible to enable live scope for ResourceSet implementations other then the XtextResourceSet, e.g. the standard ResourceSetImpl implementation?
   

To avoid outdated scopes after programmatically changing the model, you'll need to enable "live scoping" via org.eclipse.xtext.ui.resource.LiveScopeResourceSetInitializer. See JavaDoc for an explanation.
...