Project

Profile

Help

Revision d2885105

Added by Debbie Lockett 9 months ago

Fix documentation bug 4874

View differences:

src/userdoc/extensibility.xml
437 437

  
438 438
      <aside>When a stylesheet or query uses integrated extension functions and is run from the
439 439
        command line, the classes that implement these extension functions must be registered with
440
        the <a class="javalink" href="net.sf.saxon.Configuration">Configuration</a>. On Saxon-PE and
441
        Saxon-EE this can conveniently be done by declaring them in a <a class="bodylink"
440
        the <a class="javalink" href="net.sf.saxon.Configuration">Configuration</a>. This can
441
        conveniently be done by declaring them in a <a class="bodylink"
442 442
          href="/configuration/configuration-file">configuration file</a>. It can also be achieved
443
        (on all editions including Saxon-HE) by subclassing <a class="javalink"
444
          href="net.sf.saxon.Transform">net.sf.saxon.Transform</a> or <a class="javalink"
445
          href="net.sf.saxon.Query">net.sf.saxon.Query</a>, overriding the method
446
          <code>applyLocalOptions()</code> so that it makes the appropriate calls on
443
        by subclassing <a class="javalink" href="net.sf.saxon.Transform">net.sf.saxon.Transform</a>
444
        or <a class="javalink" href="net.sf.saxon.Query">net.sf.saxon.Query</a>, overriding the
445
        method <code>applyLocalOptions()</code> so that it makes the appropriate calls on
447 446
          <code>config.registerExtensionFunction()</code>; or it can be done in a user-defined class
448 447
        that implements the interface <a class="javalink" href="net.sf.saxon.lib.Initializer"
449 448
          >net.sf.saxon.Initializer</a>, and that is nominated on the command line using the

Also available in: Unified diff