Keywords for SCA:
- Assemblies (component, reference, promote, properties, bindings)
- Policies (intent, policyset, WS-Policy*)
- Client & Implementation models (java, C++, php, COBOL, ... etc)
see http://www.osoa.org.
Presentation of SCA is hard to sum-up yet very interestingly layered like Spring. Analogies with Spring are also interesting:
- Assemblies => context
- Policies and intent => AOP + annotations
- Implementation Model => bean :P or so
The Java implementation model, lifecycle, asynchronous/conversational state, callback (and so on) are sadly defined through YASLF ;) (Yet Another Specific Language Feature) though Spring support should allow to bypass these specific annotations and just expose a Spring bean.
Interestingly enough the Conversational and asynchronous mechanisms seems brand new to me in SOA in general (from the implementation point of view at least) as usually this is dealt with low-level solutions like a MOM.
Basically the Spring mechanism for this maps on sca descriptors quite closely.
On the OSS implementation side for java, Tuscany and Newton (based on OSGI).

0 commentaires:
Enregistrer un commentaire