Mike opened the floodgates with: > So, I beg for some other opinions on this!
I think to a great degree, based on what I have seen Service-oriented to mean wrt/Architecture, that you are comparing apples and oranges. Classic OO techniques work well for building your domain model. Service oriented architecture is a good way to expose a much coarser-grained interface to a large chunck of business functionality, thereby hiding the details of the domain model. OO and SOA are at different levels of granularity and thus complementary if done right. Problems typically arise if you use a specific technique at the wrong granularity level (eg. OO at the coarse architetural level or SOA at the object level). As an analogy, OO would correspond to the parts of a car engine....pistons, spark plugs, pushrods, carb, etc, which are "domain objects" that interact on a fairly fine grained level. The accellerator pedal is the very coarse-grained ,Service-oriented interface, behind which all of the domain objects that interact to fullfill the application functionality (in this analogy, go faster or slower) are hidden from view. This corresponds to current Web Services architectural thinking. It also applies to the use of a services-oriented session bean facade in J2EE to hide the details of the domain entity (and other) beans. Your comparison is like trying to contrast SOAP with TCP/IP. Different levels in the "stack". ...Andrzej Chaeron Corporation http://www.chaeron.com =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
