[ISSUE 137]: Clarify the use of a binding name in a reference target -Comment on Proposal

Folks,

This is a comment on the proposal contained
in 

http://www.osoa.org/jira/secure/attachment/10500/sca-assembly-1.1-spec-cd03%2Bissue137.doc

The bullet point about "bindingName"
is not correct, in my opinion:

"o
       <binding-name> is the name of
the service’s binding to use. If it is omitted, the SCA binding is used.>
"

There are a couple of cases to consider:

a) There are multiple bindings, each
with a name.  <binding-name> is specified.

In this case, the binding-name value
*MUST* match the name of one of the bindings.  If there is no match
it is an error.

b) There are multiple bindings, each
with a name.  <binding-name> is not specified.

In this case, the SCA runtime gets to
choose which binding is used, in an implementation-dependent fashion.

However, the selection of the binding
must be with regard to the policies applied to both the reference and to
the

service binding.  The runtime *MUST
NOT* select a binding which will fail due to policy mismatch between the

reference and the service when another
binding attached to the service will not fail due to policy mismatch.

I suggest that the bullet point about
<binding-name> is modified as follows:

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

o <binding-name> is the name of
a <binding/> of the service to use.

If <binding-name> is present,
the <binding/> subelement of the target service with @name corresponding
to <binding-name> MUST be used

for the wire.[ASM600xx]

If there is no <binding/> subelement
with @name corresponding to <binding-name>, the SCA runtime MUST
raise an error. [ASM600xx]

If <binding-name> is not present
and the target service has multiple <binding/> subelements, the SCA
runtime MUST choose one of the

<binding/> elements to use for
the wire which satisfies the mutual policy requirements of the reference
and the service. [ASM600xx]

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

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:  

From:
David Booz <>

To:


Date:
22/05/2009 13:37

Subject:
[sca-assembly] NEW ISSUE: Clarify the
use of a binding name in a reference target

Note to Issue editor:

Please feel free to rename the attached document to match the issue# when
attaching it to JIRA. Thanks.

TARGET: SCA Assembly PRD/CD03

DESCRIPTION: Reference targets can specify the name of a service binding

that should be used for invocations through that reference. This is described

in the spec here:

2786 by that target service. To do so,
a wire target MAY be specified with a syntax of

2787 "componentName/serviceName/bindingName".
[ASM90004]

The problem is that this capability is not described in the section on
wires, which

only describes the "component/serviceName" formulation for a
reference target.

PROPOSAL:

See attached Word document. My proposal is in section 5.4 ONLY. I don't
know

why there are some many other things change marked.

(See attached file: sca-assembly-1.1-spec-cd03+issuexxx.doc)

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:[attachment "sca-assembly-1.1-spec-cd03+issuexxx.doc"
deleted by Mike Edwards/UK/IBM] ---------------------------------------------------------------------

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