Thank you Radu, I think many would approve such a scenario. Speaking for myself, most of the time in these transformations we do not even need EE capabilities.

Thanks Radu, for the explanation. I didn't realize this might be a grey issue, because as far as I know you can only use this when running in Oxygen (even if it is an external call). However, perhaps you consider about including a default transformation scenario with Saxon PE or HE, since the curren...

Hi, I am missing the Ant scenario "ANT (with Saxon 9 EE XSLT support)". It is gone in Oxygen 23.0, build 2020111805. Without it, I cannot use XSLT 2.0 or 3.0 transformations by default. However, when I add the libraries manually like in the scenario "ANT (with Saxon 9 EE XSLT support)" from Oxygen 2...

Thank you Octavian for the explanation

Hi, I fail to understand how the attribute expansion works in Oxygen. The XPath "element[@attribute]" in sch:rule/@context is always reporting even if the attribute is optional in the XSD and missing in the XML. Shouldn't the schematron fail to report since it is an optional attribute and the XPath ...

In an XQuery Update script, whenever I try to use an XPath 3.1 map expression, the script fails in XML Refactoring ("To use XPath 3.1 syntax, you must configure the XPath parser to handle it"). However, when I run the same XQU with a Transformation scenario on Saxon EE, it works without problems. Is...

While content completion runs smoothly, element view feels broken in some context. When there is an xs:alternative definition, the default behavior is: if there is no other element declaration of the same name (anywhere) in the schema, elements view does not offer anything. The test alternative is n...

Thank you Radu, this works. Only issue there is with this workaround there is an error from Saxon in the transformation scenario: Programmname: Saxon-EE XQuery 9.7.0.19 Fehlerlevel: warning Beschreibung: net.sf.saxon.tree.linked.DocumentImpl@754b7981 Updated document discarded because it was not rea...

Thanks. I tried the script you named, it works without problems. Can you reproduce with the following script? Am I missing something in the serialisation options? Again, it works in the transformation scenario and only fails when called from the XML refactoring menu. Input: <?xml version="1.0" encod...

Thanks, this would be a great enhancement.

As a workaround I will use document-uri(), but I wanted to avoid having to use function chaining like replace(document-uri(),tokenize(document-uri(),'/')[last()],'') (is there a simpler way for saying "give me the path of the current file"?)

Thanks!

https://www.oxygenxml.com/doc/versions/ ... iptor.html

I want to make the path of the current XML file available to the XQuery update script in my custom refactoring operation.

Is it possible to pass ${cfdu} in the descriptor file?

My XML file contains two predefined XML entities: """ and "&". I am confused by the following behaviour: * when I run my XQU script using a transformation scenario, the entities are untouched (= everything is OK) * when I run my XQU script using a custom refactoring operation, the entities are expan...