Hi Chang, Thank you very much for reply..
On Fri, Apr 18, 2008 at 3:03 PM, Yee-Kang Chang <[EMAIL PROTECTED]> wrote: > Hi Satya > > From [1], > > "Java Enterprise Edition (Java EE) is the standard for Java-based > enterprise applications today. While it offers a rich set of technologies, > it does not define important concepts that are inherently required in > service oriented architectures such as > - Extensibility of component implementation technologies > - Extensibility of transport and protocol abstractions > - a notion of cross-application assembly and configuration > > The Service Component Architecture on the other hand provides a > standardized but extensible assembly language and methodology that can be > layered on top of existing component models and runtimes." > > Other useful information (on this subject) is available at > http://osoa.org/display/Main/SCA+Resources and a good introductory article > is [2]. > > Hope this helps. > > [1] http://osoa.org/pages/viewpage.action?pageId=3980 > [2] http://www.davidchappell.com/articles/Introducing_SCA.pdf > > --- > > Hi there, > > I am new to SCA stuff. I am not able to understand why we need SCA > specification as we already have J2EE specifications with which we can > create services and deploy them. More over to my knowledge we have Spring > frame work etc.. > > Why are we going for SCA. > > What are the substantial differences that made us to adopt SCA? > > Thanks in advance. > > Cheers, > Satya >
