Dear CXF-D-OSGi users, I've been trying for some times to distribute my OSGi-based application on several machines, using CXF D-OSGi to implement distributed services. I managed to get some very simple examples working (like HelloWorld), but as soon as I try to adapt these examples to my "real-world" needs, I'm getting stuck. The problem comes from the implementations of databinding provided by CXF. JAXB doesn't support passing an object through its interface type. Let's say I want to have an interface Person, which might be implemented by several classes, my HelloWorld service can not take a Person as argument.. Quite cumbersome when we want to create well-architectured applications... On the other hand, AEGIS is able to deal with interfaces, but it doesn't support types that don't have a default constructor... Well.. I can implement default constructor for all of my classes, but what happens when using libraries? A very simple example is the java.util.UUID....
This finding made me gave up on using D-OSGi, but, unfortunatley, it seems to be the only mature implementation of OSGi remote services, that can easily be integrated with Spring DM.... So is there another databinding implementation that does not have these constraints, and that can be used by CFX? Or any workaround to get things working with JAXB or AEGIS? Any help would be appreciated. Regards, Lorie. -- View this message in context: http://cxf.547215.n5.nabble.com/Use-of-CXF-D-OSGi-with-complex-distributed-services-tp3315295p3315295.html Sent from the cxf-user mailing list archive at Nabble.com.
