Naming comments added. More important, we have here a generic composition system. At the same time, we are using asComposedDocument to bring at the level of a movement all the information which is necessary to generate movements in certain kinds of rules (trade model, transformation, etc.). We could call this a generic movement rewriting model and asComposedDocument builds it, with BPM interfaces and movement generator interfaces. However, "composed document" could be related to other things. One approach could be to consider that composed document follows a given relation (ex. specialise) to virtually populate a document (ex. a movement) with subobjects and add to the document any "methods" which are acquired through specialise. This would be a very generic concept of composition: it not only composes document subcontents (objectValues) but also composes classes through inheritance. Other applications could be considered in many fields. I think this is a really nice pattern.

git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@35002 20353a03-c40f-0410-a6d1-a30d3c3de9de