Re: [sca-bindings] [Issue 2] Proposal version 3: How to implement SCAcallbacks using SOAP

Folks,

I believe that what we previously decided
regarding these descriptions of how to implement specific

capabilities of SCA using a given binding
is that they would form non-normative examples in an

appendix in the relevant bindings specification.

So, the idea is that a proposal like
Anish's would be ONE way of doing callbacks with SCA over web

services (SOAP), but would not rule
out other ways of doing it.  What it would show is that:

a) there IS a way to implement the callback
capability over web services

b) the example will encourage implementers
to provide callback in this way and if so, then it would give

a way to improve interoperability -
if both ends implement according to the example, they should interoperate.

As for the @callback annotation for
WSDL - the main purpose is for SCA usage (to provide the same capability

that we have in Java interfaces with
the @callback annotation) - but of course if a WSDL with such an annotation

is encountered by a non-SCA web services
client, that client can choose to interpret it in the way that SCA defines....

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:
Anish Karmarkar <>

To:
OASIS Bindings <>

Date:
29/10/2008 23:58

Subject:
Re: [sca-bindings] [Issue 2] Proposal
version 3: How to implement SCA callbacks using SOAP

I forgot to mention that when this proposal is combined
with Mike's idea 

of defining a WSDL extension to indicate the callback interface (similar

to the @Callback Java annotation), what we have is a WS-Callback 

specification (I know, yet another WS-Splat spec). Such a spec could be

a stand-alone spec independent of SCA and would result in non-SCA 

systems being able to talk to SCA services that offer bi-directional 

interfaces.

-Anish

--

Anish Karmarkar wrote:

> Attached.

> I have converted the HTML version to Word, so that it is easy for
folks 

> to comment and make inline changes.

> 

> The big change between v2 and v3 is the addition of faults. My initial

> inclination was to define our own faults, but it turns out WS-Addressing

> has some pre-defined faults which fit our purpose. So, I have reused

> those faults.

> 

> One thing I'm not clear on is whether the TC wishes to define this

> SOAP-specific callback mechanism as *one* of the ways callbacks can
be 

> implemented when using SOAP or *the* way callbacks are implemented
when 

> using SOAP. My inclination is to say *the* way, otherwise we have
to 

> invent ways (metadata such as policySets, ws-policy assertion, WSDL

> extension, Java annotation) to convey when it is required.

> 

> Comments?

> 

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

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

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