Hi Raymond, Thanks for the update, it's clear now. I resume my tests and investigation to migrate from JEE to OSGi.
Thanks again, Regards JB -----Original Message----- From: "Raymond Feng" <[email protected]> Date: Sat, 24 Oct 2009 09:11:16 To: <[email protected]>; <[email protected]>; David Bosschaert<[email protected]> Cc: tuscany-dev<[email protected]> Subject: Re: [DISCUSS] Enterprise remote service Hi, Please see my comments inline. Thanks, Raymond -------------------------------------------------- From: "Jean-Baptiste Onofré" <[email protected]> Sent: Friday, October 23, 2009 10:29 AM To: "David Bosschaert" <[email protected]> Cc: <[email protected]> Subject: Re: [DISCUSS] Enterprise remote service [[snip]] > The Tuscany SCA implementation is interesting especially with the quality > of service available. Nevertheless, it requires a dependency to Tuscany > SCA in the client (the java API for example). What's your concern of the dependency? From OSGi perspective, there is no Tuscany SCA API dependency. You just code your OSGi application following the Remote Services using the standard and SCA related (in the effort of being standardized) properties. Tuscany SCA is the Remote Service Admin implementation behind the scene and it is transparently to OSGi users. There are a few samples that would help you: http://svn.apache.org/repos/asf/tuscany/java/sca/samples/dosgi-dynamic-calculator/dosgi-calculator.png http://svn.apache.org/repos/asf/tuscany/java/sca/samples/dosgi-dynamic-calculator/ http://svn.apache.org/repos/asf/tuscany/java/sca/samples/dosgi-dynamic-calculator-operations/ In SCA, the protocols (bindings) and QoSs (policies) are declarative. The Tuscany runtime is highly composable and extensible and you can decide which bindings/policies should be enabled/included. Tuscany already has a rich set of bindings, including Web Service, RMI, JSONRPC, JSONP, ATOM, JMS, and EJB. You can add your own if yours is not there. BTW, Tuscany has a databinding framework that supports various databindings out of the box, such as JAXB, SDO, DOM, AXIOM, and JSON. The framework handles data transformations automatically based on the source/target data types. > > What do you think of a "pure" RMI implementation ? We already have the RMI support. In fact, the samples above use RMI to connect the calculator and its operations. > > Thanks again, > Regards > JB > [[snip]]
