Our XSL policy causes a WARN message to appear in the system.log file. How can we avoid it?

[stephen-soosaim]

When we receive SOAP from client most of the request having trouble to use Remove security Header policy. When we invoke remove security policy getting below warning message frequently and it will be impacting system.log file.

Can anyone having same issue and if you have solution can you please help me. I am suspecting these kind of issue with security header is not in the proper format or it could be any other issue. Can you please help me.

policy:RemoveSecurityHeader NIOThread@2 WARN STEPDEFINITIONS.XSL - CompiledXSLResourceContentHandler$2.warning() : ' The source document is in namespace http://schemas.xmlsoap.org/soap/envelope/, but none of the template rules match elements in this namespace '. During xsl compilation of cxsl://RemoveSecurityHeader

policy:RemoveSecurityHeader NIOThread@1 WARN STEPDEFINITIONS.XSL - CompiledXSLResourceContentHandler$2.warning() : ' The source document is in namespace http://schemas.xmlsoap.org/soap/envelope/, but none of the template rules match elements in this namespace '. During xsl compilation of cxsl://RemoveSecurityHeader

[DChiesa · Accepted solution]

It seems to me that you have a faulty XSL. The message is saying:

The source document is in namespace http://schemas.xmlsoap.org/soap/envelope/, but none of the template rules match elements in this namespace

The first couple paragraphs of this Stackoverflow answer explains what is happening in general.

What I would do:

• extract the XSL and test it against an example SOAP message, and observe any warning or error messages. Correct the XSL and replace it into the Edge policy.
• Alternatively, if the warnings persist, you can use this callout, in lieu of the standard XSL policy. This callout will capture warnings and errors and set them into context variables, rather than emitting them into the log files. But keep in mind that if you use this callout, you're basically just ignoring the warning messages. These warning messages probably are worth investigating....