Hi Radu,

I implemented it now the way you suggested and it works fine. :)

Thanks again,
Patrik

Hi Radu,

sounds like a great workaround. Will try that...

Thanks,
Patrik

Hi, I would like to change some transformer configurations for XsltOperations. I already implemented my own AuthorOperation-class for it and replaced the XMLUtilAccess.createXSLTTransformer() with the constrution of a saxon transformer. However, when running it, the messages and errors are not displ...

Just for completeness: One use-cases would be a transformation that potentially overwrites an existing file and asks the user before doing so (if the file already exists). The code looks like this: <xsl:if test="java:fileExists($myFile)"> <xsl:variable name="userDecision" as=&quo...

Hi, I lately implmeented a custom saxon instruction that allows to create a a message box or option dialog from within an XSLT. Since it turned out to be pretty easy to implement and very useful within my framework, I just wanted to share this idea - and the joy over oxygen, that even this is possib...

Hi, I think there's a bug in saxon/annotatedConfig.xsd: Within xslt element it expects exactly one occurance of extensionElement while the saxon documentation says: "The xslt element may contain one or more extensionElement children defining namespaces used for extension instructions. The exten...

I checked again and can confirm that for me the schematron validation doesn't apply to (standard-)conrefs as well. We just have a special use-case for a "copy-conref" where the referenced content is (automatically) copied into the document. And there - of course - the content is validated ...

Hi Bryan not sure about your problem with conref (from my experience, schematron validation applies to conrefs as well). But assuming you simply want to check that the attribute of a note element contains one of the valid values, your code is wrong: It checks for the existence of an additional note ...

Hi Alex,

this was just a minimized sample to demonstrate the problem. In my actual use-case I need to execute more complex xpath expressions (specified as default attributes of the element).

Patrik

Hi Ajuan, I think the problem is that each entry listed in the Results tabs holds its own position (line and column). Now when adding or removing lines, the content below it shifted and the stored positions differ from the actual positions... A simple workaround would be to process the results list ...

Hi, I implemented my own ValidatingAuthorReferenceResolver class (derived from DITAConRefResolver) and need to use findNodesByXPath inside resolveReference. In priciple this works fine but when the reference is resolved for the first time (after adding the element to be resolved or modifying in in t...

Hi Radu,

overriding the set/getAttributes methods in my already existing class BasicCIElement indeed solved that problem.

Thanks
Patrik

Hi again, I just noticed that there is another problem when using this in author mode: the additional guess element is not rendered correctly until a refresh. In your original example with the title element in section this means that the text you enter is not being bold (In my use-cases the differen...

Hi Radu,

your suggested solution with the classpath works fine and feels good. Thanks again.

Patrik

Hi Radu, Thanks for your thoughts. I'm using an xml file as configuration now and it works fine. If it turns out to be usefull I will follow your suggestion and replace this xml file by the result of an xsl transformation from the xml schema. So for me there's no need for any improvement from your s...

Hi Radu, I had no previous discussions about this yet. But I already had a customized SchemaManagerFilter - not for adding guessElement, though. With your code I could make it work adding a specific optional element. Thanks for that. :) However, I'm still looking for a comfortable way to mark the &q...

Hi, When I insert a new element oXygen will add all mandatory child elements as well, which is very nice. Now It occurs increasingly often that I add new elements to the xsd. To be downward compatible (i.e. not having to adapt all older documents), I don't want these new elements to be mandatory. Bu...

Thanks for the documentation. It worked but I realized that I need the to resolve the xincludes. However, adding an empty fallback in all xincludes is a sufficient alternative.

Regards,
Patrik

Hi Alex, thanks for the code. It works nicely for the common validation errors (missing elements, dublicate ids). But a failed xinclude still aborts loading the file. Is there maybe a way to keep the xincludes from being resolved at all? I could easily do this in my own java code. BTW: The class Par...

Hi, I'm using ParserCreator.newSchemaAwareDocumentBuilder() to load the complete book in my custom framework from java. Now it occurs quite often, that a small (and easily recoverable) bug in the xml code (non-unique id, missing included file, missing mandatory element, ...) keeps the file from bein...

Hi Lionel, you could load the file schema-aware. This way all the default and fixed attributes are expanded. But you won't be able to identify if an attribute was already set in the xml or has been added as default attribute. Here's my (simplified) code to do this: import javax.xml.parsers.DocumentB...

Hi Ionela,

I created a simplified sample that produces this behavior reliably on 16.0. However, with Oxygen 16.1 (which I installed parallel for tests) the error no more occurs. So I hope the problem will be solved when we all move on to Oxygen 17.0.

Thanks and regards,
Patrik

Thanks. :)

Hi Octavian, the behavior occurs on both my installation: 16.0 (build 2014070913) and 16.1 (build 2014112517), but only with "Use Saxon EE (schema aware) for xslt2 query binding" enabled. Unchecking this setting the schematron validation is being executed successfully. Thanks and regards, ...

Just for the record: It turned out that quite some additional conditions had to be metto produce this error. I sent a sample by email.

Regards,
Patrik

Hi Tavy, keeping queryBinding on xslt2 and adding an additional parameter "exception-handling" instead indeed solved this problem. Thanks for that. Unfortunately, now the next problem arised: When executing the generated script during validation, document('') does not return the xslt code ...

Following (invalid but still occuring) scenario: Root.xml: <Root xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:xi = "http://www.w3.org/2001/XInclude" xsi:noNamespaceSchemaLocation="Root.xsd"> <xi:include href="Child.xml"/> </Root> Child.xml: <C...

Hi, when I validate an xml document against an invalid schema (xsd) I usually get error messages about the error in the schema, which is what I'd expect. However, when I'm validating an xml document using a validation scenario configured in a framework that uses an invalid schema, I get a message bo...

Hi, Since we have quite large files and complex validation scenarios (including several schematron rules) the validation can take some seconds. Now when opening a document the automatic validation starts. When starting a validation manually before the automatic one has completed I get a message box ...

Hi, currently it can be quite difficult to find the responsible code when an exception occurs during schematron validation. Thus, I modified the skeleton script to support queryBinding "xslt3". In this mode the execution of each pattern is surrounded by an xsl:try. In the xsl:catch it repo...