On Wed, Jun 9, 2010 at 11:19 AM, Simon Laws <[email protected]> wrote: > In our binding.sca support (and tests [1]) we allow/expect a uri in > the binding to determine the location of the protocol endpoint. > ASM90005 means that we can't do this and the tests report errors. I > couldn't find a JIRA with a quick look but I haven't worked recently > on the binding.sca delegation code. If there is one, or if someone is > already working this, please shout. > > Generally I'd hope that this URI could be determined using defaults, > i.e. I wouldn't expect the application developer to be specifying it. > > If it were really required, for example, for convenience of tests, I > guess we could exploit binding extensibility and support a sub element > of <binding.ws/>. >
Right now it only really works well when using the Hazelcast based SCA binding (ie by including tuscany-binding-hazelcast-runtime). That uses the configuration that is being used for the endpoint registry so the SCA binding "just works". The problem with using other bindings for the SCA binding is in some environments we don't know what the absolute service endpoint is, eg when using web services and the webapp servlet host (and this was one of the main reasons for doing the hazelcast binding). ...ant
