The Apache Tuscany team announced today the Version 1.1 release of the
Java SCA project. Apache Tuscany is a runtime environment based on the
Service Component Architecture (SCA). SCA is a new component model that
facilitates the construction of composite applications. SCA is a set of
specifications initially developed by IBM and BEA which are now being
standardized by OASIS as part of the Open Composite Services Architecture
(Open CSA). The Tuscany SCA Java 1.1 release adds a number of features
including: (1) a JMS binding; (2) improved policy support; (3) an
implementation extension for representing client side Javascript
applications as SCA components. Jean-Sebastien Delfino and Luciano
Resende (IBM) commented in an InfoQ interview. JS, on the "widget"
implementation: "you can now include, in an SCA composition, client
components implemented as HTML + Javascript the AJAX way, running in
your Web browser, wired to server-side components using Tuscany's
JSON-RPC and ATOM bindings for example. Basically it is about embracing
Web 2.0 client components in a distributed SCA composition... We generate
some additional JavaScript after introspection of the references the
implements all the the plumbing code to support JSON-RPC and ATOM and
the Reference class wrapping the references that you can use in your
business logic. The Tuscany community will have to decide what's coming
ahead, as we're just getting 1.1 out, but I envision progress in the
following areas: simpler and more complete SCA policy support; more
policies -- making progress with the transaction policy; improved
end-to-end SCA contribution / deployment / distribution story; an SCA
domain administration application; integration with Geronimo;
improvements of the Web 2.0 bindings -- perhaps using Apache Abdera
for ATOM and adding cross-domain support to the JSON-RPC binding;
optimizations of the Tuscany databinding support; more platform
integration testing on Tomcat, Geronimo, etc." Luciano: "BPEL support
is not complete yet: services are supported, but references are not;
properties are not supported either, but they will require an extension
to the BPEL language. This may come next if it is requested by the
community. I have just updated the BPEL implementation guide."
No comments:
Post a Comment