At the time the statement was put in, there was a perception (or desire) by
some to insist that such an invocation goes to ALL the ports in the set of
available ports. This statement shuts that debate down.
I don't see why you think its untestable. As long as one and only one
invocation msg goes out on any invocation then the requirements of the
statement are met. I can imagine a testcase that has multiple WSDL ports
which if used are valid and would enable an invocation to occur. It seems
a simple matter to wire them to components that can inform a controller
component if they get invoked. It's complicated, but not untestable.
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:
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Eric Johnson <> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Anish Karmarkar <> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Cc: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|OASIS Bindings <> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|02/10/2010 08:46 PM |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [sca-bindings] BINDINGS-113: What does BWS20006 mean? |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Logged as: http://www.osoa.org/jira/browse/BINDINGS-113
-Eric.
On 02/10/2010 04:02 PM, Anish Karmarkar wrote:
> Title: What does BWS20006 mean?
>
> Spec: WS Binding
>
> Description:
> BWS20006 says --
> "When an invocation is made using an SCA reference binding with the
> wsdl.service form of wsdlElement, the SCA runtime MUST use exactly one
> port from the set of available ports for the reference (with port
> selection on a per-invocation basis permitted)."
>
> This is, at the very least, untestable. But I think it is also a
> pointless stmt. If the selection is made on a per-invocation basis,
> and if *an* invocation can involve only one endpoint (which I think it
> does), then this is a redundant statement. It can never be violated,
> but definition.
>
> Proposal:
>
> Remove BWS20006.
>
>
> -Anish
---------------------------------------------------------------------
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
