This assumes OneToOne belongs to the family of associations [ ManyToOne, OneToMany, ManyToMany ] for their respective editors and variations of editors.

Currently only partial set of descriptors support inverse. But the argument can be made that ALL of these descriptors should be part of core instead of extension AND they should support inverse by virtue of the natural fact they they are references to other objects via property.

• ObjectReferenceDescriptor (imlement inverse)
• OwningObjectReferenceDescriptor (consider moving to core out of extension)
• CollectionDescriptor

These 3 descriptors should be modeled such that they operate a shared interface whereby they can implement inverse. Such an interface would be used by the TrailsPagesService in the activateTrialsPage method.

In the end all references will implement inverse naturally and TrailsPagesService will be able to articulate all of these descriptors so all editors will function. Currently AssociationMgt editor which implements a HardOneToOne association (as opposed to pre-configured, soft set of associations specifically AssociationSelect) does not work.

here is a proposal

package org.trails.descriptor;

public interface IReferenceSupport extends Cloneable { public String getInverseProperty(); public void setInverseProperty(String inverseProperty); }