Potential Pitfall in Business Rule Composer
I was replying somebody in the Biztalk Server newsgroup, which reminded me that it's worthwhile to post about a potential pitfall in Business Rule Composer.
While dealing with XML Schemas in Business Rule Composer, it allows you to select a xsd (Schema) file from a local folder(like Schema1.xsd). Beware of this!
The Document Type property in the Property editor is filled in with just the name of the file (for ex: schema1) Instead of putting the fully qualified name like project1.schema1
You have to change it as fully qualified by editing the property in the property editor.
If you don't do this, the Policy will not list in the CallRules shape if you decide to call this from an orchestration.
While dealing with XML Schemas in Business Rule Composer, it allows you to select a xsd (Schema) file from a local folder(like Schema1.xsd). Beware of this!
The Document Type property in the Property editor is filled in with just the name of the file (for ex: schema1) Instead of putting the fully qualified name like project1.schema1
You have to change it as fully qualified by editing the property in the property editor.
If you don't do this, the Policy will not list in the CallRules shape if you decide to call this from an orchestration.
0 Comments:
Post a Comment
<< Home