Re: [sca-bindings] BINDINGS-134: The JMS Binding schema for wireFormat.jmsDefaultand operationSelector.jmsDefault is invalid

[Eric Johnson <eric@tibco.com>]

 Logged as http://www.osoa.org/jira/browse/BINDINGS-134

-Eric

On 08/17/2010 03:14 AM, Anthony Elder wrote:
> DESCRIPTION: The JMS Binding schema defines wireFormat.jmsDefault and
> operationSelector.jmsDefault as extending sca:WireFormatType and
> sca:OperationSelectorType, however those types are defined as abstract in
> the SCA core schema,  it is not valid for an element to have an abstract
> type.
>
> PROPOSAL: Add concrete complex type definitions to the JMS binding schema
> for JMSDefaultWireFormatType and JMSDefaultOperationSelectorType, and
> change the wireFormat.jmsDefault and operationSelector.jmsDefault elements
> to use those new types:
>
>    <complexType name="JMSDefaultWireFormatType">
>          <extension base="sca:WireFormatType"/>
>    </complexType>
>
>    <complexType name="JMSDefaultOperationSelectorType">
>          <extension base="sca:OperationSelectorType"/>
>    </complexType>
>
>    <element name="wireFormat.jmsDefault"
> type="sca:JMSDefaultWireFormatType"
>             substitutionGroup="sca:wireFormat"/>
>
>    <element name="operationSelector.jmsDefault"
> type="sca:JMSDefaultOperationSelectorType"
>             substitutionGroup="sca:operationSelector"/>
>
>