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) Kit and I created a page for the serivcemix-java-sca component: http://www.jbizint.org/wiki/index.php?title=Servicemix-java-sca As you can see, we're going to keep the component in a side repo until we have it working, but we'll build it in the servicemix build structure under deployables/serviceengines. So, it will be able to drop right in when we have it working. best regards, brian On 6/29/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
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 servicemix-bean is closer I guess but more complicated. Anyway, I you have any questions, feel free to ask. Jean-Sebastien, thanks for the pointers. I'll get the servicemix-bean > up and running with the new name of servicemix-java-sca, then > incorporate the tuscany stuff. > > Kit, we should figure out how we are going to work together on this? > I've got a spare svn repo we could work out of. > > -brian > > > On 6/28/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > [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 structure generate the service-unit JBI > artifacts? > > > > > > Just a thought about that translation layer... If you only need the SCA > > contribution and assembly models and the ability to read SCA assembly > > XML, you don't have to use the whole Tuscany runtime. We've > > rearchitected Tuscany SCA a few months ago to support that kind of > > scenario and make it easy to reuse / embed a subset of Tuscany modules > > in tools, generators, and platforms that are only interested in the SCA > > metadata without dragging the whole thing. > > > > The Tuscany modules are there: > > http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/ > > > > For the SCA assembly, SCA contribution and policy metadata models alone, > > grab these modules: > > assembly > > interface > > contribution > > policy > > > > Support for Java and WSDL interfaces, and Java component > implementations: > > interface-java > > interface-wsdl > > implementation-java > > > > Support for reading SCA assembly XML and handling SCA contributions: > > assembly-xml > > interface-java-xml (also introspects Java interfaces) > > interface-wsdl-xml (also "introspects" WSDL portTypes) > > implementation-java-xml > > contribution-impl > > > > These modules are self contained and should provide you with the ability > > to process SCA contributions and read SCA assembly XML, without > > dependencies on the Tuscany runtime, IoC container, etc. To draw an > > analogy with other projects, you could compare that level of function > > with packages like WSDL4J or Woden for WSDL for example: Models and the > > ability to read/write them. > > > > Hope this helps > > > > -- > > Jean-Sebastien > > > > > > > -- > Brian ONeill > Source Equity (http://www.sourceequity.com) > jBIZint (http://www.jbizint.org) > Technical Architect, Gestalt LLC (http://www.gestalt-llc.com) > mobile:215.588.6024 > -- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
-- Brian ONeill Source Equity (http://www.sourceequity.com) jBIZint (http://www.jbizint.org) Technical Architect, Gestalt LLC (http://www.gestalt-llc.com) mobile:215.588.6024
