After the recent changes the majority of endpoint reference matching now happens in the EndpointReferenceBinderImpl instead of being split between there and the builder which used to be the case. This leaves the way clear to implement the policy matching in one place. I've dropped some psuedo code there to that effect and I'll post separately on that.
The match at the moment is mostly happening at runtime. The build time call to the binder is disabled. If you look in the NodeFactoryImpl.configureNode() you can see where it could go if we turn it on. The reason we might need this is autowire. This is the last vestige of build time/non-registry based matching and looks for autowire candidates across the local composite. I'm in two minds about how to rationalize this so I'm opening a JIRA for it (TUSCANY-3425) Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
