<$BlogRSDUrl$>

Monday, December 13, 2004

Reserved Keywords and Distinguished Fields 

Just a quick issue I discovered the other day with one of my schemas. I added an element called timeout with some child elements to the schema (days, hours, minutes, seconds), promoted the child elements as distinguished fields and then tried to use the schema in my orchestration.

Every time I tried to use the promoted property days using myMessage.Blah.timeout.days, I kept getting a squiggly red line under timeout and days with the error: unexpected keyword: timeout, cannot find symbol ''

The issue is because the timeout name is an XLANG/s reserved keyword. Therefore, if you want to promote a field as a distinguished field to be used in an orchestration, then make sure that no elements exist that are named the same as XLANG/s reserved keywords in the path up to the root element.

When oh when will Microsoft junk XLANG/s and just use C#???

About the Author

You may be wondering who I am (or may not!), but I've been in the industry 16+ years working on a variety of systems from IBM mainframes as a CICS systems programmer, to developing on Unix and Windows based systems. At the moment, I'm currently working for a Microsoft Gold Partner in the UK called Solidsoft who specialise in systems integration using BizTalk Server. My position is generally dictated by what I'm doing, but normally as a solutions architect/consultant helping clients with their integration projects involving, yes you guessed it: BizTalk Server.

Disclaimer: all the views expressed here are my own and do not necessarily represent the views of Solidsoft Ltd or indeed any other company.