OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bindings message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-bindings] ISSUE-49: UPA in web service binding withEndpointReference



Folks,

3 possible solutions:

1. Remove the <element ref="wsa:EndpointReference" minOccurs="0" maxOccurs="unbounded"/>
from the XSD and jusy have the <any/> extensibility element.

Then have normative statements in the spec about the use of <wsa:EndpointReference/> elements in that place.

- allows there to be normative control of what is done with EndpointReference elements, but no schema checking

2. Nest the <wsa;EndpointReference/> elements inside an <sca:Reference/> element, which is placed in the XSD instead
of the current was:EndpointReference element.

- allows schema checking
- more effort to code

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



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:  mike_edwards@uk.ibm.com



From: Eric Johnson <eric@tibco.com>
To: Simon Holdsworth/UK/IBM@IBMGB
Cc: sca-bindings@lists.oasis-open.org
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 -
Simon_Holdsworth@uk.ibm.com





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








[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]