|
|
Its hard to think of a particular case in a B2B scenario where you would define a service that accepts any type of XML document, but for testing purposes we have found it very useful to have a generic Service that accepts any document, and does some very simple processing. xCommerce has a special XML Template called {System} {ANY} designed to accept any XML document as Input or Output. So if you define the input for a Service or Component using {System} {ANY} the issue becomes how do you map its structure/content which you don't know and could be anything at runtime?
|