We have a situation where a sending system is sending a message which conforms to a schema which includes an <xs:any minOccurs="0"/> element. I have access this XSD so could (in theory) create a PI message type. However, the message type can't handle the <any> element - when designing the mapping you don't have access to the elements which could be replaced into the <any> element.
Does any one have ideas, work arounds, to handle source messages whose XSD contains an <any> element?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.