Steve Jones wrote: > With OO the language was of secondary importance to the philiosphical > shift that OO represented. So it should be with SOA, but as with OO > we become obsessed with the technology and ignore the mental shift, > mainly because software vendors and developers find it very hard to > sell mental shifts whereas they can sell any TLA as "10% whiter than > the previous brand of Sudsy".
Perhaps many still do ignore the mental shift. The power of Java's mobile code model is what makes OO an integral part of SOA applications for me. When you use mobile code, your programming model doesn't change from OO to data to OO in transit in distributed systems. Instead, you get to use OO continuously without worry about transformations. Of course you have to have enough faith and forsight into the benefits of this model to buy into it and use Java as your neutralization/mediation layer. Sure, you might have plenty of OO->Data/Data->OO integration points in your enterprise, but those points are the well known, well defined points because they are legacy or otherwise unchanging points which you can develop once, and meld them back into your enterprise view/SOA. Gregg Wonderly ------------------------ Yahoo! Groups Sponsor --------------------~--> Something is new at Yahoo! Groups. Check out the enhanced email design. http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> 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/
