Just an update
I put a diagram, and a little more text up on:
http://www.jbizint.org/wiki/index.php?title=SCA
To keep things focused, I deleted the verbage around a potential SCA
JBI component implementation.
I added a diagram and Jean-Sebastien's BigBank example (with a few alterations)
Sounds good. If you already have something set up...that's fine with me.
Kit
Brian O'Neill wrote:
All,
OK. So I officially started a new service engine. Guillaume, I
figured I would use servicemix-bean as a template. Does that make
sense to you?
Jean-Sebastien, thanks for the pointers.
On 6/29/07, Brian O'Neill [EMAIL PROTECTED] wrote:
All,
OK. So I officially started a new service engine. Guillaume, I
figured I would use servicemix-bean as a template. Does that make
sense to you?
Sure, though I would have started with something more simple like
servicemix-saxon, but
L.S.,
Just trying to grasp what the problem/question is...
So, if I understand correctly, the servicemix-sca component will be
somewhat different from any other JBI component. We won't be building
an SCA container as a service engine (like you would do for e.g. EJBs),
but rather build some
I do think we need a SE like servicemix-sca (should be renamed to
servicemix-tuscany i guess) to host the Java annotated SCA pojo.
I see the translation between the SCA assembly to a JBI assembly as
something somewhat independant from ServiceMix core that could be
reused either at the tooling
kitplummer (im)Agreed...and I believe based on my limited knowledge of
Tuscany that updating the TuscanyRuntime to be able to deploy a SCA POJO
should be straight forward - and simpler with the EmbeddedSCADomain.
I also agree on the tooling to provide the mapping between an SCA
Composite to
[snip]
Brian O'Neill wrote:
OK, per Guillaume's suggestion perhaps we start anew basing everything
on 0.90 sca.
So, what are peoples thoughts towards the design of the translation
layer?
Should we leverage Tuscany's parsing capabilities to read in the SCA
contribution?
Then, from the parsed
Gert,
Correct. What we've been discussing most recently is the SCA
translation layer that would convert the lingo as you described. I
wouldn't even call this a component.
The second approach I believe also works (creating an SCA SE), but I
think we believe the SCA translation layer would
Completely agree. We'll need a means of running the annotated java as
well as the translation layer.
So, lets assume for now we need a servicemix-tuscany SE, and a
sca-jbi-translation plugin for maven. (just so it is easier to talk
about)
With respect to the implementation.jbi/, i haven't
[snip]
Guillaume Nodet wrote:
Jean-Sebastien said that the apis are quite stable now, so I guess
the best way would be upgrade to the latest released version.
Maybe Jean-Sebastien can provide more inforamtions here.
Imo, the tuscany code has changed so much so that it may be
better to try
Kit Plummer
Advanced Programs
Raytheon Missile Systems
520.360.4729 (cell)
520.545.9346 (desk)
kitplummer (im)Thanks again Jean-Sebastian.
At this point I think Guillaume is correct - we need to look at the SE.
I'm _guessing_ that the current TucsanyRuntime class gets simplified,
or replaced
Jean-Sebastien said that the apis are quite stable now, so I guess
the best way would be upgrade to the latest released version.
Maybe Jean-Sebastien can provide more inforamtions here.
Imo, the tuscany code has changed so much so that it may be
better to try uinderstanding how the SE works and
Guillaume, I think we figured out how to build/install the latest
Tuscany, referencing it from the servicemix-sca pom.xml. I'm sure by
the time we have this stuff straight Tuscany will be at 1.0 - or so. ;}
On to the problem of getting up-to-date with Tuscany. The existing test
case
13 matches
Mail list logo
