Search found 12 matches
- Thu Jan 07, 2021 3:19 pm
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 309
Re: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
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.
- Wed Dec 30, 2020 11:53 am
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 309
Re: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
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...
- Tue Dec 29, 2020 7:51 pm
- Forum: Common Problems
- Topic: Missing the Ant with Saxon EE transformation scenario in Oxygen 23
- Replies: 6
- Views: 309
Missing the Ant with Saxon EE transformation scenario in Oxygen 23
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...
- Wed Jun 17, 2020 10:38 am
- Forum: Common Problems
- Topic: Schematron schema-aware attribute expansion
- Replies: 2
- Views: 321
Re: Schematron schema-aware attribute expansion
Thank you Octavian for the explanation
- Tue Jun 16, 2020 7:23 pm
- Forum: Common Problems
- Topic: Schematron schema-aware attribute expansion
- Replies: 2
- Views: 321
Schematron schema-aware attribute expansion
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 ...
- Fri Feb 22, 2019 1:04 pm
- Forum: XQuery
- Topic: Saxon EE not available in Refactoring? Oxygen 19.1
- Replies: 1
- Views: 1110
Saxon EE not available in Refactoring? Oxygen 19.1
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...
- Mon Sep 03, 2018 5:00 pm
- Forum: Feature Request
- Topic: XSD 1.1: elements view works poorly with xs:alternative
- Replies: 1
- Views: 1436
XSD 1.1: elements view works poorly with xs:alternative
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...
- Wed Aug 29, 2018 3:10 pm
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 2780
Re: Special entity & breaks in custom refactoring XQuery Update operation
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...
- Wed Aug 29, 2018 10:21 am
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 2780
Re: Special entity & breaks in custom refactoring XQuery Update operation
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...
- Wed Aug 29, 2018 9:48 am
- Forum: Other Issues
- Topic: Can I use Oxygen variables with custom refactoring descriptor file?
- Replies: 4
- Views: 1552
Re: Can I use Oxygen variables with custom refactoring descriptor file?
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!
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!
- Tue Aug 28, 2018 6:08 pm
- Forum: Other Issues
- Topic: Can I use Oxygen variables with custom refactoring descriptor file?
- Replies: 4
- Views: 1552
Can I use Oxygen variables with custom refactoring descriptor file?
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?
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?
- Tue Aug 28, 2018 4:04 pm
- Forum: XQuery
- Topic: Special entity & breaks in custom refactoring XQuery Update operation
- Replies: 5
- Views: 2780
Special entity & breaks in custom refactoring XQuery Update operation
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...