sca-bindings message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-bindings] BINDINGS-129: Problems with the Extension Points in theXSD for binding.jca
- From: Simon Holdsworth <simon_holdsworth@uk.ibm.com>
- To: Mike Edwards <mike_edwards@uk.ibm.com>
- Date: Thu, 15 Apr 2010 10:05:24 +0100
Mike, thanks for the response, in
this case I'm happy with the proposed resolutions to the jca and jms bindings,
agree with Anish on the endpoint reference change to the binding.ws proposal.
Regards, Simon
Simon Holdsworth
Mike Edwards/UK/IBM@IBMGB wrote on 15/04/2010 09:48:55:
> [image removed]
>
> Re: [sca-bindings] BINDINGS-129: Problems with the Extension Points
> in the XSD for binding.jca
>
> Mike Edwards
>
> to:
>
> OASIS Bindings
>
> 15/04/2010 09:56
>
>
> Simon,
>
> On your two points:
>
> 1. I think that the text that you mention does not need changing.
> If any text is required to explain <sca:extensions/>
> it should be in the SCA Assembly specification (note to self - I
> need to address this in the Assembly TC)
>
> 2. For the subelements of JCA that currently use <any/> for
> extensibility, I do not propose to change these.
> This is consistent with the approach used in the similar changes
> made in the Assembly TC, where we adopted
> a "minimum change" approach and left alone the bulk of the
<any/>
> extension points, modifying only 4 cases
> where there was a known UPA clash problem.
>
>
> 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:
>
> Simon Holdsworth/UK/IBM@IBMGB
>
> To:
>
> OASIS Bindings <sca-bindings@lists.oasis-open.org>
>
> Date:
>
> 15/04/2010 08:50
>
> Subject:
>
> Re: [sca-bindings] BINDINGS-129: Problems with the Extension Points
> in the XSD for binding.jca
>
>
>
>
>
>
> A minor comment on the proposed resolution; the JCA binding spec has
> a specific section that talks about extensibility, section 2.1:
>
> The JCA Binding allows further customization of the binding element
> and its subelements with vendor specific attributes or elements.
> This is done by providing extension points in the schema; refer to
> Appendix A, “JCA XML Binding Schema: sca-binding-jca-1.1.xsd” for
> the locations of these extension points.
>
> I suppose this is generic enough that there is no need to change the
> text, although it might be worth mentioning the sca:extensions element.
>
> Also the sub-elements of binding.jca and many of their children also
> support extension via elements and attributes in other namespaces,
I
> guess we are not proposing to change that, just adding the
> sca:extensions element where its necessary. That means two
> different ways of adding extensions, which may be confusing.
>
> Regards, Simon
>
> Simon Holdsworth
>
> Eric Johnson <eric@tibco.com> wrote on 14/04/2010 17:37:53:
>
> > [image removed]
> >
> > Re: [sca-bindings] BINDINGS-129: Problems with the Extension
Points
> > in the XSD for binding.jca
> >
> > Eric Johnson
> >
> > to:
> >
> > Mike Edwards
> >
> > 14/04/2010 17:44
> >
> > Cc:
> >
> > OASIS Bindings
> >
> > Logged as: http://www.osoa.org/jira/browse/BINDINGS-129
> >
> > -Eric.
> >
> > On 04/14/2010 03:43 AM, Mike Edwards wrote:
> >
> > Target: sca-jcabinding-1.1-spec-cd03-rev5.pdf
> >
> > Description:
> >
> > The SCA XSDs mix two different forms of extensibility and this
> > causes significant problems such as UPA errors.
> >
> > The two forms of extensibility are:
> >
> > 1) The use of substitution groups for the extensibility of:
> >
> > implementation
> > interface
> > binding
> > wireFormat
> > operationSelector
> > importBase
> > exportBase
> >
> > 2) The use of
> >
> > <any namespace="##other" processContents="lax"
minOccurs="0"
> > maxOccurs="unbounded"/>
> >
> > for extensibility in many locations
> >
> >
> > A UPA problem potentially exists in any place where ONE or MORE
of
> > the elements in the list 1) above is declared
> > to be used within another element in combination with 2) in a
> > sequence or choice where it may occur that one of the
> > list 1) elements is validly succeeded by an <any/> of the
form in
> > 2). IF an extended version of any of the 1) elements
> > is created, in a non-sca namespace (this is REQUIRED for any
non-
> > standard extension), then a UPA error will be
> > reported whenever such an extension is used.
> >
> > This occurs in the XSD sca-binding-jca-1.1-cd04.xsd
> >
> > <complexType name="JCABinding">
> > <complexContent>
> > <extension base="sca:Binding">
> > <sequence>
> > <element
name="outboundConnection"
> >
type="sca:JCAOutboundConnection" minOccurs="0"
/>
> > <element
name="inboundConnection"
> >
type="sca:JCAInboundConnection" minOccurs="0"
/>
> > <element
name="outboundInteraction"
> >
type="sca:JCAOutboundInteraction" minOccurs="0"
/>
> > <element
name="inboundInteraction"
> >
type="sca:JCAInboundInteraction" minOccurs="0"
/>
> > <element
name="property" type="sca:Property" minOccurs="0"
> >
maxOccurs="unbounded" />
> > <any
namespace="##other" processContents="lax" minOccurs="0"
> >
maxOccurs="unbounded" />
> > </sequence>
> > <attribute name="connectionInfo"
type="anyURI"
> use="optional" />
> > <attribute name="initialContextFactory"
type="anyURI"
> >
use="optional"/>
> > <attribute
name="jndiURL" type="anyURI" use="optional"/>
> > </extension>
> > </complexContent>
> > </complexType>
> >
> > The sca:Binding base contains both wireFormat and operationSelector
> > elements - these then clash with the <any/> extensibility
> >
> > Proposal:
> >
> > Replace the <any/> extensibility with extensibility using
the
> > sca:extensions element as follows:
> >
> > <complexType name="JCABinding">
> > <complexContent>
> > <extension base="sca:Binding">
> > <sequence>
> > <element
name="outboundConnection"
> >
type="sca:JCAOutboundConnection" minOccurs="0"
/>
> > <element
name="inboundConnection"
> >
type="sca:JCAInboundConnection" minOccurs="0"
/>
> > <element
name="outboundInteraction"
> >
type="sca:JCAOutboundInteraction" minOccurs="0"
/>
> > <element
name="inboundInteraction"
> >
type="sca:JCAInboundInteraction" minOccurs="0"
/>
> > <element
name="property" type="sca:Property" minOccurs="0"
> >
maxOccurs="unbounded" />
> > <element
ref="sca:extensions" minOccurs="0" maxOccurs="1"
/>
> > </sequence>
> > <attribute name="connectionInfo"
type="anyURI"
> use="optional" />
> > <attribute name="initialContextFactory"
type="anyURI"
> >
use="optional"/>
> > <attribute
name="jndiURL" type="anyURI" use="optional"/>
> > </extension>
> > </complexContent>
> > </complexType>
> >
> >
> > 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
> >
> >
> >
>
> > 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
> >
> >
> >
> >
> >
> >
> >
>
> >
>
> > 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
> >
> >
> >
> >
>
>
>
> 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
>
>
>
>
>
>
>
>
> 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
>
>
>
>
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]