[EMAIL PROTECTED] wrote:
why are you passing facades to this method ? why don't you just pass the bare documentation property to the method ? (end of quote) I see at least two reasons for that : - when I generate documentation for a parameter, I need its name (to get something like "@param paramName param comment") and the parameterFacade makes it possible to get it - when I generate documentation for an operation, I need the list of its parameters to integrate their documentation. That way the call in the template would be as simple as $documentationGenerator.getOperationDocumentation($operation) for the whole documentation block. [EMAIL PROTECTED] wrote: there's something wrong because in that case it's better to put the logic in the facades themselves (end of quote) It's precisely why I suggested to override getDocumentation in subclasses of ModelElementFacade in the first place, before I realized the enormous amount of metafacade model modifications it would imply. -- Sébastien Arbogast _________________________________________________________ Reply to the post : http://galaxy.andromda.org/forum/viewtopic.php?p=2074#2074 Posting to http://forum.andromda.org/ is preferred over posting to the mailing list! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
