You can use SimpleModelNavigation to address your need. In a
PropertiesEditionElement you can create an SimpleModelNavigation that
let you define a reference to navigate before defining the
StructuralFeature in your EditionElement. For instance, if you have a
metamodel with an EClass "Person" having a containing feature typed
"Address" and an Address having an EAttribute "street", you can display
the street of a person in the EEF properties view.

To do that, create an PropertiesEditionElement "street" in the
PropertiesEditionComponent "Person". Create a SimpleModelNavigation in
this PropertiesEditionElement and set the "address" reference to its
"feature" refrence. Back to your street EditionElement, you can choose
the "street" attribute for your model reference. And the generation
takes care of this!

For the moment, the limitation of this system is the need to have the
"Address" in the Person. If there is no address, EEF will throw an
Exception. I'm currently working on a "Smartest" ModelNavigation able to
create element.