Re: [Modus-devs] XML descriptor of linked contentObjects, WAS: Collections of content objects and performance

[Sean A C. <se...@co...>]

On Friday, Nov 1, 2002, at 09:32 US/Pacific, Nathan Dintenfass wrote:
> ----------------------------------------------------------------------- 
> -
>   <field name="related"
>     label="Related Press Releases"
>     type="org.bacfug.modus.fields.contentObject"
>     multiple="yes">
>    <objectType name="modustest.contentObjects.pressRelease"/>
>   </field>
> ----------------------------------------------------------------------- 
> ----
>
> Well, this is not flushed out yet, but the idea is that there is a  
> field
> type called "contentObject" that knows how to deal with having a
> contentObject (or a collection of them) as its value.  That way, the
> baseContentObject nor the baseField needs to have the machinery for  
> dealing
> with this case -- we can build a field type that knows about this,  
> since it
> is seems like a special case.  Thus, I say this is a fieldType of
> org.bacfug.modus.fields.contentObject (which probably should go back to
> being contentObjectCollection) and I then need to tell it which
> contentObject type it will hold.

Ah, OK. But then isn't type="org.bacfug.modus.fields.contentObject"  
somewhat redundant? Do you *need* the ability to specify multiple  
container types? Do you even *want* that ability? It seems to me that  
it's just an implementation detail - the important part is the  
underlying type, not the collection type itself.

"I have always wished that my computer would be as easy to use as my  
telephone.
  My wish has come true - I no longer know how to use my telephone."
-- Bjarne Stroustrup