Re: [sca-bindings] sca:endpointReference versus wsa:EndpointReference forWSBinding

This is interesting, as the overall schema
still have UPA issues when you try to extend bindings using a different
namespace (e.g Tuscany extensions to SCA Schema). I'll be proposing some
shema changes to address overall UPA issues, which will include removing
the <xsd:any>  from Binding WS schema and this might allow us
to go back to use wsa:EndpointReference directly if the Binding TC wish
to do so.

- Luciano 

Luciano Resende
Open Source SOA - Apache
Tuscany
4400 N 1st St, San Jose - CA 
notes: Luciano
Resende/Westford/IBM
internet IBM: 
internet ASF:  blog @ developerWorks : link
Apache Tuscany blog: link

Great things are not done by impulse
but by a series of small things brought together
- Vincent Van Gogh 

From:      
 Eric Johnson <>
To:      
 Luciano Resende/Westford/IBM@Lotus
Cc:      
 
Date:      
 03/16/2010 01:31 PM
Subject:    
   Re: [sca-bindings]
sca:endpointReference versus wsa:EndpointReference for WS Binding

Hi Luciano,

As I recall we were forced into doing this to resolve a limitation with
XML Schema and the use of "xsd:any" leading to a "unique
particle attribution" error.

http://www.osoa.org/jira/browse/BINDINGS-49

-Eric

On 03/16/2010 12:19 PM, Luciano Resende wrote: 
Is there a particular reason why the
ws binding schema defines it's own endpointReference element based on wsa:EndpointReferenceType
without extending it, instead of just referencing the wsa:EndpointReference
directly ? 

Here is the snipet from the ws binding xsd :

<complexType name="WebServiceBinding">
        <complexContent>
            <extension base="sca:Binding">
                <sequence>
                    <element
name="endpointReference" type="wsa:EndpointReferenceType"
                    
        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"/>
            </extension>
        </complexContent>
    </complexType>

This requires composites to have the following when configuring the ws
binding. Note that although endpointReference is an element defined from
sca namespace, we still need to use the child elements based on the wsa
namespace.

                <binding.ws
wsdlElement="http://helloworld#wsdl.binding(HelloWorldSoapBinding)">
                   <endpointReference>
                    
 <wsa:Address xmlns:wsa="http://www.w3.org/2005/08/addressing">http://localhost:8085/services/HelloWorldWebService1</wsa:Address>
                   <endpointReference>
                </binding.ws>

[1] http://tools.oasis-open.org/version-control/svn/sca-assembly/SCA_XSDS/sca-binding-ws-1.1-cd04.xsd
[2] http://www.w3.org/2006/03/addressing/ws-addr.xsd

- Luciano 

Luciano Resende
Open Source SOA - Apache
Tuscany
4400 N 1st St, San Jose - CA 
notes: Luciano
Resende/Westford/IBM
internet IBM: 
internet ASF:  blog @ developerWorks : link
Apache Tuscany blog: link

Great things are not done by impulse
but by a series of small things brought together
- Vincent Van Gogh