ESB TransformationService does not set the context property DocumentSpecName of the output message to be the target schema type after transform

  • Article

ESB TransformationService does not set the context property DocumentSpecName of the output message to be the target schema type after transform

 

Problem:

===========================================

 

After performing XML Transform with ESB TransformationService, your ESB Send Pipeline may report the following error:

 

Error: Document type 'https://<NameSpace>' does not match any of the given schemas.

 

However you confirm the transformed message schema properly exists and has been deployed.

 

Cause:

============================================

 

We found this is an issue that ESB TransformationService does not set the context property DocumentSpecName of the output message to be the target schema type after transform. However the XML assembler component will check if current message schema matches the schema list in this context property. If not, it reports the schema mismatching error.

 

Work around:

============================================

 

You can use a normal map(not ESB TransformationService) or receive port which will properly set the context property as a work around. A permanent fix may be provided in a hotfix or future release of ESB toolkit.