Re: [wsn] RE: [wsdm] Notify wrapped vs Soap body

[David Hull <dmh@tibco.com>]

Title: Notify wrapped vs Soap body

Sedukhin, Igor S wrote:

I would just reconcile and make wsnt:Message be a container of xs:any and that's it. At least it won't be different from S:Body.

Just as a blue-sky question, what would it take for wsnt:Message to be S:Body?  That is, move items like SM endpoint and NP endpoint to SOAP headers.  I realize that this would not address boxcarring.  I've always been uncomfortable with a bespoke approach to boxcarring, but I don't have an alternative to suggest at the moment.

 

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749

 

---

From: Springer, Ian P. [mailto:ian.springer@hp.com]
Sent: Thursday, March 24, 2005 12:01 PM
To: Sedukhin, Igor S; wsdm@lists.oasis-open.org
Cc: wsn@lists.oasis-open.org
Subject: RE: [wsdm] Notify wrapped vs Soap body

From my experience, xs:anys pretty much always cause serialization hell.

 

Regarding UseNotify, it would be nice if a producer could choose to require UseNotify. I can think of two ways this could be done:

 

1) Add a NotifyRequired xs:boolean resource prop to the NotificationProducer portType

2) Add a notifyRequired xs:boolean attribute to the wstop:Topic element

The latter would allow the flag to be specified per topic but would be more difficult for clients to ascertain. In either case, I think a NotifyRequiredFault would need to be added to the subscribe operation.

 

Ian

---

From: Sedukhin, Igor S [mailto:Igor.Sedukhin@ca.com]
Sent: Thursday, March 24, 2005 11:48 AM
To: wsdm@lists.oasis-open.org
Cc: wsn@lists.oasis-open.org
Subject: [wsdm] Notify wrapped vs Soap body

So the wsnt:Notify/wsnt:NotificationMessage/wsnt:Messaage is xs:anyType while soap:Envelope/soap:Body is a container of xs:any. This creates a serialization hell since any given object needs to be serialized sligtly differently, in principle. More over objects that serialze directly in value could not be sent unwrapped, but could be sent Notify wrapped. Since indication of UseNotify is at the subscriber's will, it may result in a bunch of interoperability problems.

-- Igor Sedukhin .. (igor.sedukhin@ca.com)
-- (631) 342-4325 .. 1 CA Plaza, Islandia, NY 11749