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: NEW ISSUE: The JMS Binding schema for wireFormat.jmsDefault andoperationSelector.jmsDefault is invalid



TARGET: SCA JMS Binding Specification cd04

TITLE: The JMS Binding schema for wireFormat.jmsDefault and
operationSelector.jmsDefault is invalid

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


   ...ant



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