> Obviously when designing a system which is meant to stay the course we > need to make it as adaptable, reusable and evolvable as possible.
Right. IIRC there is such a system that has proven to be quite well designed and is has now been around for a decade. > That after all is the whole point of SOA. Fine, but since there is such a system....why design a new one that is not even an evolution of the existing, proven one? Why use build upon a paradigm (specific interfaces) that is known for its poor success regarding reusability and evolvability. Jan ________________________________________________________________________ _______________ Jan Algermissen, Consultant & Programmer http://jalgermissen.com Tugboat Consulting, 'Applying Web technology to enterprise IT' http://www.tugboat.de Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
