[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [sca-bindings] [Issue 2] Proposal version 3: How to implementSCA 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]