On Wed, Sep 17, 2008 at 9:52 AM, Simon Laws <[EMAIL PROTECTED]>wrote:
> Back in September last year the parts of the sca-binding-webservice.xsd > schema marked below with chevrons were removed. We don't support > wsdlLocation at the moment so I can see why that would be the case but we do > still process EndpointReference elements. Were these elements removed for > technical reasons? > > > <schema xmlns="http://www.w3.org/2001/XMLSchema"; > targetNamespace="http://www.osoa.org/xmlns/sca/1.0"; > xmlns:sca="http://www.osoa.org/xmlns/sca/1.0"; > xmlns:wsdli="http://www.w3.org/2004/08/wsdl-instance"; > xmlns:wsa="http://www.w3.org/2004/12/addressing"; > elementFormDefault="qualified"> > > >>>>>>>>> <import namespace="http://www.w3.org/2004/08/wsdl-instance"; > schemaLocation="wsdli.xsd" /> > >>>>>>>>> <import namespace="http://www.w3.org/2004/12/addressing"; > schemaLocation="ws-addr.xsd" /> > <include schemaLocation="sca-core.xsd"/> > > <element name="binding.ws" type="sca:WebServiceBinding" > substitutionGroup="sca:binding"/> > <complexType name="WebServiceBinding"> > <complexContent> > <extension base="sca:Binding"> > <sequence> > > >>>>>>>>>> <element ref="wsa:EndpointReference" > minOccurs="0" > maxOccurs="unbounded"/> > > <any namespace="##other" processContents="lax" > minOccurs="0" > maxOccurs="unbounded"/> > </sequence> > <attribute name="wsdlElement" type="anyURI" use="optional"/> > > >>>>>>>>>>> <attribute ref="wsdli:wsdlLocation" > use="optional"/> > > <anyAttribute namespace="##any" processContents="lax"/> > </extension> > </complexContent> > </complexType> > </schema> > > Simon > I can appreciate that inclusion of these schema imports are problematic in this form as the runtime would keep trying to retrieve them acorss the network when started. Can't be just distribute these specific schema versions and reference them locally. I note that the ws policy schema import has also been removed from sca-policy.xsd. Simon
