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

[Anthony Elder <ant.elder@uk.ibm.com>]

As discussed on last weeks binding call here is the updated proposal to fix
the JMS binding schema wireFormat/operationSelector issues:

- add concrete types for JMSDefaultWireFormatType and
JMSDefaultOperationSelectorType, and update the wireFormat.jmsDefault and
operationSelector.jmsDefault elements to use those new concrete types.

- update the JMSResponse complex type to use a ref for the wireFormat

An SVN diff of those changes is:

Index: src/main/resources/sca-binding-jms-1.1-cd04-rev1.xsd
===================================================================
--- src/main/resources/sca-binding-jms-1.1-cd04-rev1.xsd    (revision
986604)
+++ src/main/resources/sca-binding-jms-1.1-cd04-rev1.xsd    (revision
986690)
@@ -85,7 +85,7 @@

    <complexType name="JMSResponse">
       <sequence>
-         <element name="wireFormat" type="sca:WireFormatType"
minOccurs="0"/>
+         <element ref="sca:wireFormat" minOccurs="0" maxOccurs="1"/>
          <element name="destination" type="sca:JMSDestination"
minOccurs="0"/>
          <choice minOccurs="0">
             <element name="connectionFactory"
type="sca:JMSConnectionFactory"/>
@@ -166,9 +166,21 @@
    <element name="binding.jms" type="sca:JMSBinding"
             substitutionGroup="sca:binding"/>

-   <element name="wireFormat.jmsDefault" type="sca:WireFormatType"
+   <complexType name="JMSDefaultWireFormatType">
+      <complexContent>
+         <extension base="sca:WireFormatType"/>
+      </complexContent>
+   </complexType>
+
+   <complexType name="JMSDefaultOperationSelectorType">
+      <complexContent>
+         <extension base="sca:OperationSelectorType"/>
+      </complexContent>
+   </complexType>
+
+   <element name="wireFormat.jmsDefault"
type="sca:JMSDefaultWireFormatType"
             substitutionGroup="sca:wireFormat"/>

-   <element name="operationSelector.jmsDefault"
type="sca:OperationSelectorType"
+   <element name="operationSelector.jmsDefault"
type="sca:JMSDefaultOperationSelectorType"
             substitutionGroup="sca:operationSelector"/>
 </schema>

Regards,

    ...ant



                                                                           
             Eric Johnson                                                  
             <eric@tibco.com>                                              
                                                                        To 
             18/08/2010 21:26          Anthony Elder/UK/IBM@IBMGB          
                                                                        cc 
                                       sca-bindings@lists.oasis-open.org   
                                                                   Subject 
                                       Re: [sca-bindings] BINDINGS-134:    
                                       The JMS Binding schema for          
                                       wireFormat.jmsDefault and           
                                       operationSelector.jmsDefault is     
                                       invalid                             
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           
                                                                           




 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"/>
>
>

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