Hi Brian, SCA is an infrastructure for building composite applications the parts of which could be coming from implementations that might be running on different platforms / runtime technologies, that might be using different protocol bindings and databindings. Typically, one might have to go and code such compositions and put in lots of plumbing code to address connecting to various containers, dealing with wire level protocols, data formats and so on. But with SCA all (or atleast most) of this is spared. All that you need to do is 'define' the solution/application composition as a Composite (in a .composite file) and simply deploy it. The SCA runtime takes care of interpretting this composition and creating all the necessary plumbing around it - all during runtime.
Hope this helps to start on further questions :) Thanks - Venkat On 6/15/07, Brian O'Neill <[EMAIL PROTECTED]> wrote:
All, Excuse the ignorance, but I'm trying to understand the benefits of designing applications using SCA. From the sample applications in Tuscany, it appears as though Tuscany functions much like Spring; it provides a means to map logical services to their implementations (dependency injection), and then adds a layer to compose services on top of that. The only SCA specific files I see in the samples are the composition files. (e.g. Calculator.composite) Thus, it leads to the question, is that all it takes to create a "SCA-compliant" application? -brian -------------------- Brian O'Neill Technical Architect, Gestalt LLC mobile: 215.588.6024 http://weblogs.java.net/blog/boneill42/ <http://weblogs.java.net/blog/boneill42/>
