On 09/01/07, Linus Tolke <[EMAIL PROTECTED]> wrote:
Hello...
Hello!
I must confess that I had a much more complex set of interfaces in mind
than the simple one-type-for-all-Model-Elements that Bob has drawn. The
simple, one-type-for-all-Model-Elements is simple to implement but on
the other hand, I agree with Tom that the benefit gained from it is
probably low too.
I think to have a ModelElementFacade will help clarify the code for
future developers coming along.
I didn't envisage extending this interface into individual façades for
each model element type in UML1.4 as we need to hide the
implementation as much as we can. But there is a balance with the need
for ease of use dealing with known objects with useful methods rather
than always calling the model and dealing with generic Objects. So I
did think it a good idea to cover some of the basics that would exist
across UML implementations. e.g. ClassFacade and AssociationFacade
How about considering façade wrappers for those model elements that
exist in both MOF1.4.1 and MOF2
All else should remain handled by our existing Model interface which
hides such detail of the implementation.
Bob.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
