Hi David, Option (1) sounds good to me. Two follow-up questions so far: (a) I need to create the services at runtime (it's not just that I'm missing the dependency on the bundle that defines the interface -- it's really created at runtime depending on some protocol that the user defines in the GUI of my RCP, which he eventually exposes via a "Publish" button). Do you have any tips on how to generate the class file that defines the service? As far as I understand I will need to create a temporary java file and programmatically write java code and then compile it in the background in order to pass the class to the service registry. I'm thinking of a counterpart to the DynamicClientFactory which handles all the technical parts. Ideally I would have some control on the wsdl generation to make sure that the wsdl looks the same for the same protocol, independent of the cxf version. (b) Does the "service.exported.interfaces=" support wildcards like, e.g. "org.foo.MyService*", or is '*' a very special value?
Thanks! Bernd -- View this message in context: http://old.nabble.com/DOSGi---Dynamic-Web-Services-%28no-service-interface-at-compile-time%29-tp26545343p26588092.html Sent from the cxf-user mailing list archive at Nabble.com.
