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&q...

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: "&quot;" and "&amp;". 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 refactor...