SOAP properties in non request/reply interactions

I believe I left a piece out of the sketch I sent of how to define 
in-out-alternateOut.  Namely, how to define a SOAP property analogous to 
the [alternate reply endpoint] abstract property, on a par with the 
http://www.w3.org/@@@@/@@/addressing/feature/ReplyEndpoint property in 
the Addressing 1.0 SOAP module.

Is it possible to add properties to a module after the fact, or would we 
need to define a new module somewhere?  If so, should it contain all the 
properties it needs, or could it reference the addressing 1.0 module to 
pick up Destination, SourceEndpoint, ReplyEndpoint and so forth?

I'm assuming here that if reply endpoint and fault endpoint need to be 
regarded as SOAP properties, then an alternate reply endpoint would, 
too.  If not, I'd be curious to know why.

Received on Tuesday, 15 March 2005 16:36:03 UTC