Next in thread →
Next in month →
Re: [sca-bindings] ISSUE-49: UPA in web service binding withEndpointReference
Folks, This reminds me of the the old song "there's a hole in my bucket"... ...which ends up where it started... ;-) The reason that sca:EndpointReference works when wsa:EndpointReference does not is simply that the extension point <any /> has @namespace="##other", which says that any extension elements must come from a namespace OTHER than the SCA namespace. The crucial difference between sca:EndpointReference and wsa:EndpointReference is that sca:EndpointReference is from the SCA namespace and thus CANNOT be mistaken for any element that would qualify as an <any/> - hence changing to sca:EndpointReference from wsa:EndpointReference solves the UPA problem while retaining the extensibility called for... PS The version of "There's a hole in my bucket..." with Harry Belafonte from the 1960's is especially good. Yours, Mike. Strategist - Emerging Technologies, SCA & SDO. Co Chair OASIS SCA Assembly TC. IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain. Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431 Email: From: ashok malhotra <> To: Eric Johnson <> Cc: Mike Edwards/UK/IBM@IBMGB, OASIS Bindings <> Date: 21/10/2008 08:50 Subject: Re: [sca-bindings] ISSUE-49: UPA in web service binding with EndpointReference Just one question. If we go in this direction why do we need sca:EndpointReference? Why can't we use wsa:EndpointReference? All the best, Ashok Eric Johnson wrote: > > Mike Edwards wrote: >> >> 3. Create an <sca:EndpointReference/> element which is of the type >> wsa:EndpointReferenceType >> >> - given that wsa:EndpointReference is of the type >> wsa:EndpointReferenceType, this means that the sca:EndpointReference >> is identical in usage to the wsa:EndpointReference >> - allows schema checking >> - zero more work to code than the current schema >> >> >> I recommend solution #3..... > +1 > > -Eric. >> >> >> >> Yours, Mike. >> >> Strategist - Emerging Technologies, SCA & SDO. >> Co Chair OASIS SCA Assembly TC. >> IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain. >> Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431 >> Email: >> >> >> From: Eric Johnson <> >> To: Simon Holdsworth/UK/IBM@IBMGB >> Cc: >> Date: 17/10/2008 19:16 >> Subject: Re: [sca-bindings] ISSUE-49: UPA in web service binding >> with EndpointReference >> >> >> ------------------------------------------------------------------------ >> >> >> >> Logged as: _http://www.osoa.org/jira/browse/BINDINGS-49_ >> >> -Eric. >> >> P.S. I took the editorial liberty of changing the title of the issue >> in Jira. >> >> Simon Holdsworth wrote: >> >> TARGET: SCA WS Binding Specification cd01 >> >> DESCRIPTION: >> >> The schema for binding.ws calls for the following construct: >> >> <sequence> >> <element ref="wsa:EndpointReference" minOccurs="0" >> maxOccurs="unbounded"/> >> <any namespace="##other" processContents="lax" >> minOccurs="0" >> maxOccurs="unbounded"/> >> </sequence> >> >> Which leads to a UPA error it you try and validate against it. For >> UPA see _http://en.wikipedia.org/wiki/Unique_Particle_Attribution_ >> >> The schema is valid in the sense that it's valid and well formed XML >> but you will get a UPA validation error if your .composite file has >> an EndpointReference element within a binding.ws element. The problem >> being that the validator doesn't know if the EndpointReference >> belongs to the <EndpointReference> or <any> schema elements. >> >> PROPOSAL: >> >> It seems difficult to fix this kind of problem and maintain the >> ability to support EndpointReference validation and binding.ws >> extensibility without changing the structure of binding.ws. >> Resolution to be determined. >> >> >> >> Simon Holdsworth >> STSM, SCA Bindings Architect; Master Inventor; OASIS SCA Bindings TC >> Chair >> MP 211, IBM UK Labs, Hursley Park, Winchester SO21 2JN, UK >> Tel +44-1962-815059 (Internal 245059) Fax +44-1962-816898 >> Internet - .com_ >> <mailto:> >> >> >> >> ------------------------------------------------------------------------ >> / >> / >> >> /Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire >> PO6 3AU/ >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >> >> >> >> ------------------------------------------------------------------------ >> >> / >> / >> >> /Unless stated otherwise above: >> IBM United Kingdom Limited - Registered in England and Wales with >> number 741598. >> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire >> PO6 3AU/ >> >> >> >> >> >> > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Next in thread →
Next in month →