OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-tx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Issue 059 - Protocol event indications are not ws-addressing faults


This is identified as WS-TX issue 059.

Please ensure follow-ups have a subject line starting "Issue 059 -
Protocol event indications are not ws-addressing faults".

-----Original Message-----
From: Tom Rutt [mailto:tom@coastin.com] 
Sent: Tuesday, May 09, 2006 1:23 PM
To: ws-tx
Subject: [ws-tx] NEW ISSUE: Protocol event indications are not
ws-addressing faults

Nature of Problem:

With the resolution of Issue 52, the specifications (coord, at, ba) have

two kinds of indicaitons:

Faults (definined in ws coord) which map to ws-addressing fault model.

"notifications" (from ws at, ba) which do not map to ws addressing 
faults, and which are treated as
first class "requests" from ws addressiing perspective.

Mapping the second kind of indication to a soap fault, but not a ws 
addressing fault, will inevitably cause
confustion for implementers of this spec.

Proposed solution:

Instead of mapping the "notificaitons" to soap fault syntax, define a 
new schema type
{ProtocolEventIndication) which conveys the proper syntax for the 
contents of these protocol notifications.

Have each individual protocolEventIndication be mapped to this new 
syntax, as a proper ws addressing request message.

-- 
----------------------------------------------------
Tom Rutt	email: tom@coastin.com; trutt@us.fujitsu.com
Tel: +1 732 801 5744          Fax: +1 732 774 5133




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]