tag:blogger.com,1999:blog-1914853297990362461.post2670978246106307291..comments2009-04-02T16:57:40.368-07:00Niraj Jnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1914853297990362461.post-18622221207059006642008-08-28T08:16:00.000-07:002008-08-28T08:16:00.000-07:00Rob ,<br><br>Agreed that :What is SOA to one company is JBOWS to another.<br><br>What I have typically seen in Fortune 100 kinda companies is that SOA corresponds to a - central owner of common services and the SOA platform so that there can leverage across the enterprise. And hence my comment about Master API.<br><br>Now JBOWS is actually SOA , but not a definition the SOA group within an Enteprise would agree with. Well ofcourse if you do not have an SOA group in the Enterprise , the JBOWS is your SOA and there is no disagreement.Niraj Jhttp://www.blogger.com/profile/06480714242783122078noreply@blogger.comtag:blogger.com,1999:blog-1914853297990362461.post-75049305313484717672008-08-28T07:56:00.000-07:002008-08-28T07:56:00.000-07:00"...SOA concept of coming up with a master API that will be used by everyone is failing."<br><br>Interesting. I've never heard "master API" as being one of the concepts of SO.<br><br>Since SOA doesn't have a common definition used by all/most, stories such as "SOA adoption down" or "SOA failures up" or "SOA being used more broadly" are all bunk.<br><br>What is SOA to one company is JBOWS to another. Many consider to be WOA to be different from SOA--even though the creator of the WOA term explicitly defined WOA as a refinement of SOA.<br><br>I guess my point is that we shouldn't read much of anything into these adoption stories.Rob Eamonnoreply@blogger.com