Hi Joel, sorry for the late reply.
I had a look to your prototype (thanks for providing it), it runs fine on my machine. Some questions/comments: 1) What's the relation between the folder projects and the folder plugins? Is there a maven/ant script to build the content of the plugins folder? I imported the projects into Eclipse and found some compile problems in org.apache.axis2 and tuscany_osgi_sca_binding_axis2. But since the plugins folder does not contain tuscany-osgi-sca-binding-axis2, I got the impression that's not used currently (maybe could be deleted?). 2) The config directory under TuscanySample could be deleted, the configuration directory contains the required configuration, isn't it? 3) Shipper You provided two implementations, Java and Spring. In the implementation (the Java Class) there shouldn't be any difference? Why are the service and reference tags sub-tags of implementation-spring? I thought, implementation, reference and service should be on the same level? 4) WebService Access from Shipper to Customer How does it work exactly? Is the reference entry (SCACustomer) really required? My impression it that the entry "<property name="customer" ref="SCACustomer"/>" together with the CustomerService.wsdl is enough (at least it still worked after deleting the reference entry in spring_sample.scdl file :-) Thanks and best regards Nicole -----Original Message----- From: Hawkins, Joel [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 29, 2006 11:01 PM To: [email protected] Subject: OSGi sample posted Jim, Nicole, I've posted my OSGi sample on my people.apache.org site - http://people.apache.org/~jhawkins/Tuscany/TuscanySample.zip There's a readme that describes the sample and how to run it. I've also included a snapshot of my Eclipse work area. The Tuscany binaries are based on a synch of HEAD performed yesterday. I've got a few things to finish up (like support for scdl imports) before creating a patch I'd be happy with, so please bear with me. I've come to the conclusion that we need to develop some packaging conventions for deploying apache functionality into OSGi. I'm aware of the Eclipse Orbit project, which is providing some common packaging of Apache (and other non-eclipse) projects for consumption within Eclipse. Is this something that Apache should be doing for itself, either on a per-project basis, or under the province of a project like Felix? I believe that if we adopt some common conventions, it'd make generating virtual bundles (and supporting OSGi as an optional deployment target in general) a good bit easier. Cheers, Joel The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
