Lists Home |
Date Index |
> > This kind of design is quite similar to AFs, in fact, but its OOP
orientation make it
> > quite powerful (because polymorphism in data would be leveraged by
polymorphism in code).
> This seems very close to AFs. In fact I think from a markup perspective
> you need are *exactly* AFs
> What I think you're adding is a XML serialization/mapping layer which is
AF aware. So
> once you've processed your instance as a particular AF, you end up with
> objects that conform to interfaces that inherit from one another. Sounds
> The dynamic proxy stuff in Java ought to make this kind of thing
straight-forward to right.
Is there a role for the "Demeter" method here?