Re: [sca-assembly] NEW ISSUE: Spec is unclear if callback binding namesneed to be distinct from forward binding names

[Mike Edwards <mike_edwards@uk.ibm.com>]

Logged as:
 http://www.osoa.org/jira/browse/ASSEMBLY-156


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:	Simon Nash <oasis@cjnash.com>
To:	OASIS Assembly <sca-assembly@lists.oasis-open.org>
Date:	27/06/2009 09:37
Subject:	[sca-assembly] NEW ISSUE: Spec is unclear if callback binding names need to be distinct from forward binding names

---

TARGET: Assembly Model Specification

DESCRIPTION: Spec is unclear if callback binding names need to be distinct
from forward binding names

The Assembly Model spec says that all binding names on a service or
reference need to be unique.  It isn't competely clear whether this
uniqueness requirement extends across the complete set of forward bindings
and callback bindings.  There are at least two possible options:

  1. Every binding (forward and callback) needs to have a name that
     is different from every other binding (forward and callback).

  2. Every forward binding needs to have a name that is different
from
     every other forward binding, and every callback binding
needs to
     have a name that is different from every other callback
binding.

Option 1 seems unnecessarily restrictive.  It disallows some very
common cases, such as:

   <service name="MyService">
       <binding.ws uri="someURI" />
       <callback>
           <binding.ws />
       <callback>
   </service>

This is illegal under option 1 because the names of both the
forward and callback bindings default to the service name MyService.
The solution is to specify an explicit name on either the forward
or callback binding, which is unintuitive and unnecessary.

Option 2 seems better than option 1 because it avoids the need to
specify the unnecessary explicit binding name in the common case
above, while still preserving name uniqueness among forward bindings
and name uniqueness between callback bindings.

PROPOSAL:

Replace ASM90002 by the following:

When a service or reference has multiple bindings, all non-callback
bindings of the service or reference MUST have unique names, and all
callback bindings of the service or reference MUST have unique names.
[ASM90002]  This uniqueness requirement implies that only one non-callback
binding of a service or reference can have the default @name value,
and only one callback binding of a service or reference can have the
default @name value.


   Simon



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