Well, changing the type from CollectionDescriptor to TrailsPropertyDescriptor for associationDescriptor seems to mitigate the tapestry coercian exception.
 
Now if I had checkin priv's it could already have been fixed.

Best regards
Ken in nashua

Subject: RE: Link Hierarchy - natural modeling
Date: Tue, 12 Feb 2008 16:27:01 -0500

Likewise...
 
Are all page service parameters associations ONLY collections?
 

public class TrailsPagesServiceParameter implements Serializable

{

private PageType pageType ;

private IClassDescriptor classDescriptor ;

private Object model ;

private CollectionDescriptor associationDescriptor ;
 
Why the lapse in association modeling?
 
There are plenty of ObjectReferenceDescriptors that could be supported including OwningObjectReferenceDescriptors.
 
What I am trying to do is utilize the LinkRenderer for a non-collection oriented association. The associationDescriptor parameter is not delivering for me.

Best regards
Ken in nashua

Subject: Link Hierarchy - natural modeling
Date: Tue, 12 Feb 2008 16:21:40 -0500

Given the following taxonomy...
 
    AbstractLinkComponent
          ^
         | |
    TrailsLink
          ^
         | |
    ModelLink
          ^
         | |
    EditLink
 
In the TrailsLink implementation... Why is associationDescriptor  specifically hardwired to CollectionDesacriptor?
 
Does the natural world mandate that every KIND of association be a collection?

Best regards
Ken in nashua

---

Shed those extra pounds with MSN and The Biggest Loser! Learn more.

---

Shed those extra pounds with MSN and The Biggest Loser! Learn more.

---

Climb to the top of the charts! Play the word scramble challenge with star power. Play now!