On Tue, Mar 16, 2010 at 12:41 PM, Luciano Resende <[email protected]> wrote: > The WS Binding OASIS schema defines it's own version of > EndpointReference instead of using the wsa:EndpointReference [1], but > it seems that we are using the wsa:EndpointReference in Tuscany > interchangeably as the schema was allowing extensibility using > <xsd:any> from other namespaces. As part of applying new OASIS schema, > I'm removing this extensibility to avoid UPA conflicts, and thus will > change the usage of wsa:EndpontReference to sca:endpointReference. > > Note that I have also sent a question to the OASIS Binding TC trying > to clarify why they have chosen this path. > > Please let me know if you see any issues around these changes... > > [1] > http://tools.oasis-open.org/version-control/svn/sca-assembly/SCA_XSDS/sca-binding-ws-1.1-cd04.xsd
It seems that OASIS created it's own version of endpointReference because of UPA issues [1]. I have been able to fix the UPA issues and still use the wsa:EndpointReference... so, instead of moving Tuscany code to use sca:endpointReference, it might be worthwhile to propose the fix to OASIS and use wsa:EndpointReference as we have today. [1] http://www.osoa.org/jira/browse/BINDINGS-49 -- Luciano Resende http://people.apache.org/~lresende http://twitter.com/lresende1975 http://lresende.blogspot.com/
