Raymond Feng wrote:
Hi,
The following JavaOne session may give you a good idea to start. I
believe the two presenters have done some work. It would be nice to see
them come aboard to join the efforts.
http://developers.sun.com/learning/javaoneonline/2008/pdf/TS-5870.pdf
Here is a summary of the analogy of the concepts between SCA and JBI.
SCA JBI
----------------------- ------------------------------
Implementation SE (Service Engine)
Binding BC (Binding Component)
Composite SA (Service Assembly)
Component SU (Service Unit)
Service SU Provides
Reference SU Consumes
Wire Connection
Thanks,
Raymond
--------------------------------------------------
From: "Charuka Jayarathna" <[EMAIL PROTECTED]>
Sent: Wednesday, June 25, 2008 3:24 PM
To: <[email protected]>
Subject: writing binding extension to integrate JBI BC
Hello,
I am trying to integrate JBI with Tuscany. I followed Apache
implementation of JBI , "servicemix" to get familiar with a JBI
implementation. I would like to clarify following before proceeding
any further. I appreciate your guide and thoughts. Please correct me
if I am not going the correct direction.
In the proposal, you suggest to write a tuscany binding extension to
run a JBI binding component. Does that mean to transfer any specific
binding type defined according to JBI standard to one protocol type so
that tuscany runtime could handle the binding type?.
thank you
charuka
The SCA / JBI paper on osoa.org [1] may help you position SCA and JBI
and find interesting integration opportunities.
Here's my view of this, maybe simplistic, but here it is anyway:
- JBI == SPIs and architecture for runtime developers who develop server
runtimes
- SCA == programming and assembly model for business component developers
- integration opportunity == enable business component developers to
develop and assemble business components using the SCA model and run
them on a JBI-based server runtime
- how == provide software that reads SCA contributions (archives
containing your SCA component implementations), SCA .composite files
that describe their assembly, turns them into JBI configuration, and
deploys and runs the components on a JBI server
- technology picks == Tuscany's assembly and contribution models to read
and process the SCA artifacts, ServiceMix or another JBI implementation
for the JBI runtime
- staging == 5 steps
(1) take a scenario (e.g Tuscany's store or Bigbank) and study its SCA
artifacts
(2) write the corresponding required JBI configuration for ServiceMix
(3) understand the mapping and write the translation code from SCA
artifacts to JBI configuration
(4) bring-up the scenario and get it working end to end, demo it and
explain it to people and get feedback
(5) now you really know what you're up to :) refine all of the above
There's probably other less interesting integration opportunities:
a) implement a JBI service engine for POJOs written according to the
SCA/Java programming model
b) implement the minimum subset of the JBI SPIs enabling ServiceMix
Binding Components and Service Engines to be reused and plugged into
Tuscany
but the SCA on top of JBI story I've described above is more interesting
IMO.
[1] http://www.osoa.org/display/Main/Relationship+of+SCA+and+JBI
Hope this helps.
--
Jean-Sebastien
