I'm working right now on an extension of the binding-sca-runtime code
which uses an XML databinding. Our current implementation, in
contrast, will prefer Java serialization and then JAXB/XML
serialization (when no databinding is otherwise specified).
One test which fails for me, then, is itest/service-reference, not
surprising since it includes interface:
@Remotable
public interface BComponent {
....
String fooC(ServiceReference<CComponent> cComponent);
and, while our ServiceReference impl is Java-serializable, it is not
JAXB/XML serializable.
------
Just curious if anyone thinks this is an important use case to
support. It clearly could only be a Tuscany-ism, right, and most
likely only over the default binding (or conceivably other bindings
using Java-serialization as wire format. Is it supposed to work
across JVMs? Nodes?
Does anyone think we should just remove the test so as to be clear
that we don't support this? That might be my preference... before
we release version 2 to be clear that we don't. But maybe there is a
good reason for it?
Scott
