Some IEPD developers choose to break extension schemas into multiple documents by subject area to allow them to reuse the schemas more granularly in various exchanges.

This default binding behaviour implies that multiple bindings can exist - from one or many queues to one or many exchanges.

As you can see, multiple SOAP message exchanges are required to process transactional Web service invocations.