Re: [Modus-devs] XML descriptor of linked contentObjects

[Jeremy F. <jfi...@ma...>]

So did you ever send something only to realize moments later how stupid =
you were?

Of course the post won't know it's a field. It seems the way you =
suggested with the objectType works:

  <field name=3D"posts"
    label=3D"Posts"
    type=3D"org.bacfug.modus.fields.objectcollection"
    multiple=3D"yes">
   <objectType name=3D"modustest.contentObjects.post"/>
  </field> =20

I don't know what I was thinking.
  ----- Original Message -----=20
  From: Nathan Dintenfass=20
  To: mod...@li...=20
  Sent: Friday, November 01, 2002 2:18 PM
  Subject: RE: [Modus-devs] XML descriptor of linked contentObjects


  So, myorg.post would have to extend the objectCollection field?=20

  If that is what you are suggesting, I'm not sure I like that a =
contentObject needs to know that it could end up as a field.  That's why =
I am thinking that making a field type objectCollection and then passing =
the configuration data from the descriptor of the contentObject type =
that wants to make the link makes sense.

  Or, am I missing your point?

    -----Original Message-----
    From: mod...@li... =
[mailto:mod...@li...]On Behalf Of Jeremy =
Firsenbaum
    Sent: Friday, November 01, 2002 11:08 AM
    To: mod...@li...
    Subject: Re: [Modus-devs] XML descriptor of linked contentObjects, =
WAS: Collections of content objects and performance


      While we're on this topic, I am not sure how Jeremy's suggestion =
would work:


        <field name=3D"posts"
          label=3D"Posts"
          type=3D"org.bacfug.modus.fields.objectcollection"
          key=3D"postid"/>

      I do not understand how it knows it is dealing with the post =
component.
      Please explain.

    Sorry for the confusion. I got hung up on the objectcollection idea. =
It's supposed to read type=3D"myorg.post" which extends =
"org.bacfug.modus.fields.objectcollection" in it's descriptor. Hope that =
clarifies things.

    -Jeremy