That's a bug (the spec does allow locateService on external
services). One of the changes underway is to manage external services
as another instance context type (instance contexts manage a runtime
artifact such as a component). This will clear up the bug. I'll have
a further write-up on the changes ASAP.
Jim
On Feb 10, 2006, at 6:56 AM, Jeremy Boynes wrote:
ant elder wrote:
Does there have to be a wire?
No, there doesn't - note to self, drink coffee before doing email.
An example is something like:
sca.module:
<module xmlns="http://www.osoa.org/xmlns/sca/0.9";
xmlns:v="http://www.osoa.org/xmlns/sca/values/0.9";
name="sampleHelloworld">
<externalService name="HelloWorldService">
<interface.wsdl interface="
http://
helloworldaxis.samples.tuscany.apache.org#HelloWorldServiceImpl"/>
<binding.ws port="
http://helloworldaxis.samples.tuscany.apache.org#helloworld"/>
</externalService>
</module>
That's the same as from one of the samples that used to work so there
could be a bug there.
OTOH, and I know it's early and the coffee has not kicked in, but are
those URIs correct? Shouldn't they point to a valid location?
--
Jeremy
