RE: SOAP UML diagram

> I'm confused about what a Module is.  Why must it have at least one
> Header Block, but a Feature can exist without a Header Block?  Is a
> Module a necessary concept here?

AFAIK Modules are special types of Features that are expressed via SOAP Headers. So if I provide reliable messaging via headers like in WS-RM that is a Module. But if I provide it instead via binding to a transport that supports reliable messaging, that is just a Feature.

Ugo
 

Received on Thursday, 12 June 2003 15:27:58 UTC