Saxon Custom Extensions in XSLT are considered problems

[MattCousinsSapiens]

This is a minor issue for me, but wanted to make sure I am not overlooking an approach via settings or some existing means.

My XSL files can reference java classes directly using a homegrown extension written for Saxon. However the plugin as of now highlights these references as an issue. Is there away to get these problems ignored? Perhaps by using the fact the namespace is prefixed with "java:" as this also gets highlighted even if I am using a standard java class instead of my custom ones.

As an example:
<xsl:stylesheet version="3.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:jndiUtils="java:com.adaptik.util.JNDIUtils"
exclude-result-prefixes="jndiUtils">

<xsl:variable name="lookupURL" select="jndiUtils:getJNDILookup('url/application')"/>

Any thoughts would be appreciated, but its not breaking anything.

[pgfearo]

This requires a minor code change. A pragmatic fix would be for it to avoid verifying references to functions with prefixes bound to a URI using the “Java” scheme at the start. This behaviour could then be controlled via a user setting.

You can currently filter the associated problems listed in the problems pane, but the highlighting of the function issues will remain.