Hi, I've gotten a few comments on my recent blog entry about SCA:
http://www.iona.com/blogs/newcomer/archives/000260.html I thought perhaps this group might be interested also in a discussion on SCA. The goal of SCA is to make it easier to develop, deploy, and manage SOA based applications across multiple languages and transports. SCA is also closely related to the SOA Tools project at Eclipse: http://www.eclipse.org/stp/ Both initiatives are just getting started, so it's a good stage for discussion and feedback. One of IONA's major interests is to align the SCA assembly metadata model with the Eclipse SOA Tools project and support the mapping of the assembly model onto various runtime environments, such as JEE, Spring, and Celtix to name a few. While it is certainly possible to hand code the equivalent using WS-* specification APIs, the use of SCA defined metadata is intended to simplify the process for developers. Another way to put it, which may tie into some of the other discussions on this list, is that it is entirely possible to define good, large grained, loosely coupled interfaces for use in an SOA environment, but how easy is it to design and develop the appropriate code to implement those interfaces? And especially if you need to tie together applications created using multiple languages and middleware systems? (Which is kind of the point of SOA in the first place.) One of the large items of discussion at the SOA kickoff that I didn't mention in the blog entry is whether to emphasize the top down or bottom up approach? Right now SCA supports both, but which is more important to the industry? Similarly, SCA supports both synchronous and asynchronous MEPs. Which of these is more important for the project to focus on? Eric __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com 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/
