You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <de...@tuscany.apache.org> on 2008/10/06 12:39:44 UTC

[jira] Commented: (TUSCANY-2626) Investigate why endpoint reference and wsdlLocation are not in the sca-binding-webservice.xsd schema file

    [ https://issues.apache.org/jira/browse/TUSCANY-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637068#action_12637068 ] 

Simon Laws commented on TUSCANY-2626:
-------------------------------------

    <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>
               ...

As written currently the binding.ws schema includes both EndpointReference and and "any" extensibility element in the binding sequence which leads to UPA error during validation. I don't see an easy way around this other that removing one of the EndpointReference or any elements. 

> Investigate why endpoint reference and wsdlLocation are not in the sca-binding-webservice.xsd schema file
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-2626
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2626
>             Project: Tuscany
>          Issue Type: Task
>          Components: Specification
>            Reporter: Richard Mah
>            Assignee: Simon Laws
>
> Investigate why endpoint reference and wsdlLocation are not in the sca-binding-webservice.xsd schema file.  If there is no good reason why they have been removed, insert it back into the sca-binding-webservice.xsd schema file.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.