You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org> on 2006/08/16 18:23:13 UTC

[jira] Created: (TUSCANY-629) In sca-binding-webservice.xsd / the specification of the endpoint/port should be optional

In sca-binding-webservice.xsd / <binding.ws> the specification of the endpoint/port should be optional
------------------------------------------------------------------------------------------------------

                 Key: TUSCANY-629
                 URL: http://issues.apache.org/jira/browse/TUSCANY-629
             Project: Tuscany
          Issue Type: Bug
          Components: Specification
    Affects Versions: Cpp-current
            Reporter: Jean-Sebastien Delfino
         Assigned To: Jean-Sebastien Delfino


In sca-binding-webservice.xsd / <binding.ws> the port or endpoint attribute should be optional. An application developer should be able to specify that he wants a Web Service binding on a composite service or reference without specifying the WSDL endpoint or port, which will be specified later by a system administrator for example, or derived from default settings and (on a service) from where the composite is actually running.

I will raise this issue to the OSOA specfication workgroup.

    <complexType name="WebServiceBinding">
        <complexContent>
            <extension base="sca:Binding">
                <sequence>
                    <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
                </sequence>
                <attribute name="port" type="anyURI" use="required" />
                <anyAttribute namespace="##any" processContents="lax" />
            </extension>
        </complexContent>
    </complexType>

should be changed to:

    <complexType name="WebServiceBinding">
        <complexContent>
            <extension base="sca:Binding">
                <sequence>
                    <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
                </sequence>
                <attribute name="port" type="anyURI" use="optional" />
                <anyAttribute namespace="##any" processContents="lax" />
            </extension>
        </complexContent>
    </complexType>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org

[jira] Updated: (TUSCANY-629) In sca-binding-webservice.xsd / the specification of the endpoint/port should be optional

Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
     [ http://issues.apache.org/jira/browse/TUSCANY-629?page=all ]

ant elder updated TUSCANY-629:
------------------------------

    Fix Version/s: Cpp-current

> In sca-binding-webservice.xsd / <binding.ws> the specification of the endpoint/port should be optional
> ------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-629
>                 URL: http://issues.apache.org/jira/browse/TUSCANY-629
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Specification
>    Affects Versions: Cpp-current
>            Reporter: Jean-Sebastien Delfino
>         Assigned To: Jean-Sebastien Delfino
>             Fix For: Cpp-current
>
>
> In sca-binding-webservice.xsd / <binding.ws> the port or endpoint attribute should be optional. An application developer should be able to specify that he wants a Web Service binding on a composite service or reference without specifying the WSDL endpoint or port, which will be specified later by a system administrator for example, or derived from default settings and (on a service) from where the composite is actually running.
> I will raise this issue to the OSOA specfication workgroup.
>     <complexType name="WebServiceBinding">
>         <complexContent>
>             <extension base="sca:Binding">
>                 <sequence>
>                     <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
>                 </sequence>
>                 <attribute name="port" type="anyURI" use="required" />
>                 <anyAttribute namespace="##any" processContents="lax" />
>             </extension>
>         </complexContent>
>     </complexType>
> should be changed to:
>     <complexType name="WebServiceBinding">
>         <complexContent>
>             <extension base="sca:Binding">
>                 <sequence>
>                     <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" />
>                 </sequence>
>                 <attribute name="port" type="anyURI" use="optional" />
>                 <anyAttribute namespace="##any" processContents="lax" />
>             </extension>
>         </complexContent>
>     </complexType>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org