Configuring Proposed Values in the Context that the Content Completion was Invoked - SAXON

Post here questions and problems related to oXygen frameworks/document types.
Johann
Posts: 59

Configuring Proposed Values in the Context that the Content Completion was Invoked - SAXON

Tue Feb 21, 2017 6:54 pm

Hi everyone,

In the Author Component, I try to test
Configuring Proposed Values in the Context that the Content Completion was Invoked
from https://www.oxygenxml.com/doc/versions/18/ug-author/topics/configuring-content-completion-proposals.html#configuring-content-completion-proposals

An EE or PE version of SAXON is required to perform this configuration.

Is there a way to use another XSLT Processor in the Author Component instead of SAXON ?

Thank your for your response,

Johann
alex_jitianu
Posts: 600

Re: Configuring Proposed Values in the Context that the Content Completion was Invoked - SAXON

Thu Feb 23, 2017 4:53 pm

Hi Johann,

In theory the XSLT should run just fine with Saxon-HE (which is available in the Author Component) as long as the XSLT doesn't use any functionality available only in the PE/EE versions. If you would need access to the element for which the CC was invoked, you will run into this issue (because saxon:eval() is not available in the HE version).

Code: Select all

        <xsl:variable name="propertyElement"
            select="saxon:eval(saxon:expression($contextElementXPathExpression, ./*))"/>


Unfortunately there is no workaround for this other than using the Java API instead and implementing a SchemaManagerFilter.

Best regards,
Alex

Return to “SDK-API, Frameworks - Document Types”

Who is online

Users browsing this forum: No registered users and 1 guest