BizTalk xs:date promotion shows inconsistency?
I think I may have found an inconsistency with BizTalk promotion mechanism. Context The system is using – roughly – two orchestration super-types: The ones that are publishing business data from external sources to the enterprise data warehouse, and The ones that are subscribing to (wait for) events on the bus and provide data to other enterprise systems for day to day operations. One of the responsibilities of publisher super-type orchestrations is to notify subscriber super-type orchestrations when data is available in the warehouse. Publishers and subscribers do not know each others (no call/send shape or partner ports are allowed). This loosely-coupling behavior is supported with event messages that travel through the message box. Publishers creates the event messages for subscribes in this disconnected mode. Event messages have the same message type and only its inner element values would reveal which concept of data is available. Subscribers may h