Looks like a good change to me Raymond. It means that the client is using the same default binding stack that normal references are. I'm adding tests and using just the SCA client in isolation does highlight that we need to init() the node to get the registry up an running.
More generally we need to look at the default binding. At the moment it's restricted to one and only one remote transport. I think we need to relax this and allow the binding to decide what transport to use based on the environment it finds itself in and the configuration of the endpoint. In particular we have this situation where, in the remote endpoint case, we have to decide whether it's really remote (different JVM) or just in a different classloader, in which case an optimization is possible. I guess this is a different thread. Simon
