Re: [sca-bindings] Re: Issue BINDINGS-107

[Simon Holdsworth <simon_holdsworth@uk.ibm.com>]

OK then the proposed resolution for
BINDINGS-107 is as follows:

Overall: Remove all mention of use of
a binding element in a definitions file, along with the description of
how properties from the definitions file are overridden from the JCA binding
specification.

Detail for binding.jca (applies to JCA
CD03 pdf version)

Remove the binding.jca/@connectionInfo
attribute from the pseudo schema (line 58), description (115-118), and
XML schema appendix (line 438)
Change normative statement [BJC20001]
(line 112-114) from:
"The @uri attribute, the @connectionInfo
attribute and the inboundConnection or outboundConnection elements are
mutually exclusive and the SCA runtime MUST raise an error if more than
one is present [BJC20001]." to:
"The @uri attribute, the inboundConnection
element and the outboundConnection element are mutually exclusive and the
SCA runtime MUST raise an error if more than one is present [BJC20001]."
Remove section 5, "Binding properties"
entirely (line 245 to 303)
Remove section 6.4, "Existing Resources
specified in the definition file" entirely (line 356 to 385)

Update whole of section 7.1 "SCA
JCA Binding XML Document" to remove reference to SCA Definitions Document
as an SCA Definitions Document no longer has any conformance requirements
around binding.jca elements (lines 393-400) to:

An SCA JCA Binding XML document is an
SCA Composite Document or an SCA ComponentType Document, as defined by
the SCA Assembly specification Section 13.1 [SCA-Assembly], that uses the
binding.jca element.  An SCA JCA Binding XML document MUST be a conformant
SCA Composite Document or SCA ComponentType Document, as defined by the
SCA Assembly Specification [SCAAssembly], and MUST comply with all statements
in Appendix B: “Conformance Items”related to elements and attributes
in an SCA JCA Binding XML document, notably all "MUST" statements
have to be implemented.

----------------------------------

A corresponding change to the JMS document
to remove the use of binding elements in a definition file would be (applies
to JMS CD03 pdf version):

Remove the binding.jms/@requestConnection
attribute from the pesudo schema (line 72), description (179-181) and XML
schema appendix (line 808)
Remove normative statement BJM30007:
"If the @requestConnection attribute is specified, the binding.jms
element MUST NOT contain a destination, connectionFactory, activationSpec
or resourceAdapter element [BJM30007]".

Remove the binding.jms/@responseConnection
attribute from the pesudo schema (line 73), description (184-185) and XML
schema appendix (line 809)
Remove normative statement BJM30008:
"If the @responseConnection attribute is specified, the binding.jms
element MUST NOT contain a response element [BJM30008]".

Remove the binding.jms/@operationProperties
attribute from the pseudo schema (line 74), description (188-189) and XML
schema appendix (line 810)
Remove normative statement BJM30009:
"If the @operationProperties attribute is specified, the binding.jms
element MUST NOT contain an operationProperties element [BJM30009]".

Remove example section 7.6 "Use
of Predefined Definitions Example" (line 672 - 693)

Update whole of section 8.1 "SCA
JMS Binding XML Document" to remove reference to SCA Definitions Document
as an SCA Definitions Document no longer has any conformance requirements
around binding.jms elements (line 753 - 760) to:

An SCA JMS Binding XML document is an
SCA Composite Document or an SCA ComponentType Document, as defined by
the SCA Assembly Specification [SCA-Assembly] Section 13.1, that uses the
binding.jms element.  An SCA JMS Binding XML document MUST be a conformant
SCA Composite Document or SCA ComponentType Document, as defined by the
SCA Assembly Specification [SCA-Assembly], and MUST comply with all statements
in Appendix B: “Conformance Items” related to elements and attributes
in an SCA JMS Binding XML document, notably all "MUST" statements
have to be implemented.





Regards, Simon

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

From:	Anish Karmarkar <Anish.Karmarkar@oracle.com>
To:	sca-bindings@lists.oasis-open.org
Date:	19/11/2009 06:42
Subject:	Re: [sca-bindings] Re: Issue BINDINGS-107

---

Fine with me as well.

-Anish
--

On 11/18/2009 4:59 AM, Mike Edwards wrote:
> 
> My +1 too.
> 
> 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:                
 David Booz <booz@us.ibm.com>
> To:                
 sca-bindings@lists.oasis-open.org
> Date:                
 18/11/2009 12:47
> Subject:              
   Re: [sca-bindings] Re: Issue BINDINGS-107
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> +1 If it turns out that standardizing such a mechanism does become
> something of great utility, we can easily add it in a future version
> without breaking anything. Plus we'd have some real use cases on which
> to base the design.
> 
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:booz@us.ibm.com
> 
> Inactive hide details for Simon Holdsworth ---11/18/2009 06:06:04
> AM---Folks, here's my opinion on BINDINGS-107, I'd appreciateSimon
> Holdsworth ---11/18/2009 06:06:04 AM---Folks, here's my opinion on
> BINDINGS-107, I'd appreciate your comments/opinions.
> 
> From:                
 
> Simon Holdsworth <simon_holdsworth@uk.ibm.com>
> 
> To:                
 
> sca-bindings@lists.oasis-open.org
> 
> Date:                
 
> 11/18/2009 06:06 AM
> 
> Subject:              
   
> [sca-bindings] Re: Issue BINDINGS-107
> 
> 
> ------------------------------------------------------------------------
> 
> 
> 
> 
> Folks, here's my opinion on BINDINGS-107, I'd appreciate your 
> comments/opinions.
> 
> The main purpose of having JMS and JCA binding elements in the 
> definitions file is to allow a single JMS/JCA application to be accessed
> from several SCA references or services without having to duplicate
all 
> the details of connection and operation mapping. That's primarily
due to 
> the fact that there's no standard service definition for JMS/JCA 
> applications. Typically for service bindings, the information is going
> to be specific to each exposed service so I would expect such sharing
to 
> be mainly but not exclusively used for references.
> 
> There's no functional reason why we require this mechanism. If we
remove 
> it from the spec it doesn't reduce the capability of the bindings,
it 
> just means that SCA runtimes would possibly need to provide their
own 
> way of managing sharing of such information outside of the standard
> definitions. Given that this is not a portability/interop requirement
> I'd say its not that high a priority to be standardised. If we feel
that 
> the additional complexity that this brings to the JMS and JCA bindings
> specs is not justified, then I don't feel particularly strongly about
> removing it.
> 
> Regards, Simon
> 
> 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/
> 
> 
> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> /
> /
> 
> /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