public interface IAssociationPage extends IModelPage

{

    CollectionDescriptor getAssociationDescriptor();

    void setAssociationDescriptor(CollectionDescriptor 

                                                 associationDescriptor);

 
This design prevents OneToOne association from occurring (since it assumes all associations are collection based) in trails now that operates a OneToOne property editor.
 
Are associations explicit enough to need being spelled out like this? I kinda think they are implicit enough to be built into the descriptors (with inverse) and be dealt with automatically rather than have a dedicated interface.
 
It would have been nice to see ALL checkins that occurred in 2007 had made it aboard the recent migration. That seems reasonable instead of regressing portions of the framework and deisgning them out.
 
I am inclined to feel that the ReferenceDescriptors need to all be reworked into the main core, including the extension one(s), and remodeled to accomodate inverse, since they are all association/reference based... and then TrailsPageService logic needs to be reworked to accomodate these... then the page cycle will accomodate the whole spectrum of associations.

Best regards
Ken in nashua

---

Helping your favorite cause is as easy as instant messaging. You IM, we give. Learn more.