2 Replies Latest reply on Oct 24, 2008 2:55 PM by Newsgroup_User

    advice on vo's

      Hello all,

      I am about to create a VO that will incorporate a variable number of properties.

      These properties will be used to create aggregate values within the class.

      The basic concept is a parentVO with an unknown # of Child voS.
        • 1. Re: advice on vo's
          -Hob Level 1
          Not really sure what you're asking for advice on here... If the question is whether or not to create child vos, then yes. The point of vos is to have strongly typed objects instead of deserialized xml/json/etc... If you simply start adding properties to your VO rather than having child vos, then those properties won't be strongly typed, and thus you'll have problems binding to them.
          • 2. Re: advice on vo's
            Level 7

            "Mush15" <webforumsuser@macromedia.com> wrote in message
            news:gdt5us$ffk$1@forums.macromedia.com...
            > Hello all,
            >
            > I am about to create a VO that will incorporate a variable number of
            > properties.
            >
            > These properties will be used to create aggregate values within the class.
            >
            > The basic concept is a parentVO with an unknown # of Child voS.

            Look at HierarchicalData.

            HTH;

            Amy