Keith Babo wrote:
For the time being, I think it would be best to point to the WSDL location explicitly within the deployment. We can do this by extending the standard "interface.wsdl" element in SCA to introduce a <wsdlLocation> element. So something like this:
<sca:interface.wsdl interface="urn:switchyard-quickstarts:m1app:0.1.0-SNAPSHOT#wsdl.porttype(OrderService)"> <sy:wsdlLocation>wsdl/OrderService.wsdl</sy:wsdlLocation> </sca:interface.wsdl>
Although I said it sounds good, it made me think that we would end up with a new Model and its parser, wouldn't we? Why can't we have it like this:
It still sticks to the SCA syntax, instead of namespace we use the WSDL location, that could be a URL too.
Yeah, I think that's cleaner. So we will assume that a value specified for interface with no scheme specified resolves to a classpath local resource. We may revisit this once we get some hands on experience using the feature, but I think this is a reasonable way to move forward at this point.