AWESOME! Thanks for the slide deck. Can't wait for tomorrow. At my company we have a meeting room setup with an LCD Projector so we can all watch the show at once, it's working out great and providing us with a lot of great information.

These are great slides! They really helped to bolster my understanding of sequential convoys. Nonetheless, it seems that in the Trial version of BizTalk 2004, non-uniform sequential convoys with MSMQT seem to be broken:
- orchestrations that contain early-bound MSMQT ports with just won't build, even when you set the OrderedDelivery property to "true".
- any orchestrations that I deploy with non-uniform sequential convoys don't activate; they create Routing Failure Reports in HAT and "MSMQT failed to publish the message coming into the queue ..., because no consumer was waiting for it".

The strange thing is that these orchestrations worked fine in the Beta version. Can you comment on this?

Thanks on MSMQT I need way more information. For official support go the PSS route. Otherwise post a sample demonstrating it somewhere and I'll get someone to look at it. I'd be surprised if it wasn't an understanding issue but just to be sure.

Hi,

Excellent news on the release, and webcasts. Quick question, will teh webcasts be available for download, or just viewing on demand?

(I have LAN and no soundcard on my desktop, and soundcard and no LAN in my LapTop :-/ )

Looks like the technology supports on demand only.

We (thanks Lee) finally had a chance to look at the convoy sample problem mentioned above. The issue in in the testmessage.xml sample data file. The schema is marked as unqualified. This means that the xpath which is generated for the property promotion is only namespace qualified at the root level. The next levels of the xpath all use an empty namespace. When you look at the sample message, the root node does not have a namespace prefix so all subelements are going to inherit its namespace definition since they have the same prefix (empty). You need to do one of two things:

Put a prefix before his root node ala
<ns0:root xmlns:ns0="http://TestMessaging.Schema1">
Or change his schema definition to be qualified so that the xpath will be namespace qualified at all levels.

I tested it the first one and then it all works.

PS: You could diagnose this when you promoted properties associated with the message which failed to route that the ID field was not promoted (was not even written) to the context.

Now when you get it fixed, can you send it back and I'll link to it for everyone :)

PingBack from http://uniformstores.info/story.php?id=19078

PingBack from http://patiocushionsource.info/story.php?id=113