This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I have read about SOA but am not sure how to go about implementing SOA using J2EE.Please enlighten me.
Building a service-oriented architecture requires many inter-related parts. Some of them are technical and some of them are business-oriented. At the highest level, however, a SOA is a business strategy. And the notion of a "service" is not fundamentally a technology concept. A "service" is an abstract representation of value that a business wants to achieve with its technology.
Take note that "services" in a SOA and "web services" are not the same thing. For example, a "service" called "Create travel reservation" may use many "web services" or may not use any "web services" at all.
Part of Java EE includes an API and reference implementations that can be used to create "web services" which can then be part of a service-oriented architecture. A group of "web services" does not equate to a SOA however. The most important aspect of creating a service-oriented design is to define the "services" from a business process point of view, since business processes fundamentally define a business.
Hope this helps! [ July 31, 2008: Message edited by: James Clark ]