In some biztalk integrations with legacy systems, there are message specifications that requires a specific namespace prefix, but all biztalk messages use ns0, ns1, ns… definition to define prefix information.
To solve this problem there are two solutions :
- You can replace the prefix data in all maps output xslt, then replace the map with the changed xslt, solution explained in Jeff Lynch blog.
- Use a custom pipeline with a component that makes the necessary replacements.
If you have few maps that do not change frequently, you can implement the first solution, otherwise the second solution is better.
I have created a custom component, based on the ESB Guidance namespace component, that perform the prefix replacements. It only requires the old and the new prefix name and uses streams in the replacement for better performance.
Before use, check the regular expression replacement agains your message schemas, and see if doesn't make any unnecessary replacement.
