Section 1.10.5 of the OSOA and Section 12.5 of the OASIS Assembly Spec for this topic is shown below....
"For certain types of artifact, there are existing and commonly used mechanisms for referencing a specific concrete location where the artifact can be resolved. Examples of these mechanisms include: • For WSDL files, the @wsdlLocation attribute is a hint that has a URI value pointing to the place holding the WSDL itself. • For XSDs, the @schemaLocation attribute is a hint which matches the namespace to a URI where the XSD is found. Note: In neither of these cases is the runtime obliged to use the location hint and the URI does not have to be dereferenced. SCA permits the use of these mechanisms. Where present, these mechanisms take precendence over the SCA mechanisms. However, use of these mechanisms is discouraged because tying assemblies to addresses in this way makes the assemblies less flexible and prone to errors when changes are made to the overall SCA Domain. Note: If one of these mechanisms is present, but there is a failure to find the resource indicated when using the mechanism (eg the URI is incorrect or invalid, say) the SCA runtime MUST raise an error and MUST NOT attempt to use SCA resolution mechanisms as an alternative." Looks like currently Tuscany runtime always uses the SCA resolution mechanism to resolve the @wsdlLocation of WSDL and @schemaLocation of XSD's files, instead of using the non-SCA mechanism as suggested by specs. This issue is raised as TUSCANY-2906. But my confusion is that, the specs also says that the usage of non-SCA resolution mechanisms is discouraged. Like to take suggestions from the community, as what needs to be supported. -- Thanks & Regards, Ramkumar Ramalingam
