[
https://issues.apache.org/jira/browse/XERCESJ-1699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18008594#comment-18008594
]
Mukul Gandhi commented on XERCESJ-1699:
---------------------------------------
[~singingbush] URL of Xerces-J repos is https://github.com/apache/xerces-j.
From my point of view, the branches 'main' and 'xml-schema-1.1-dev' of this
code base repos are the most important branches of this repos. These two code
base branches are of equal importance.
The branch 'main' other than usual XML related implementations has XML Schema
1.0 implementation but not XML Schema 1.1 implementation. The branch
'xml-schema-1.1-dev' has all what branch 'main' has and additionally XML Schema
1.1 implementation.
Recently, few code repos changes not related to XML Schema have taken place on
Xerces-J branch 'main'. I think, those code repos changes should also take
place on branch 'xml-schema-1.1-dev' as well.
> While using XSD 1.1, full XPath 2.0 with CTA doesn't work in certain cases
> --------------------------------------------------------------------------
>
> Key: XERCESJ-1699
> URL: https://issues.apache.org/jira/browse/XERCESJ-1699
> Project: Xerces2-J
> Issue Type: Bug
> Components: JAXP (javax.xml.validation), Samples
> Affects Versions: 2.12.0
> Environment: Windows 10, 64-bit
> Reporter: Yitzhak Khabinsky
> Assignee: Mukul Gandhi
> Priority: Major
> Fix For: 2.12.1
>
> Attachments: IFRS15_CBC_In_XercesJ.xsd,
> XercesJ_TZ20171231_IFRS15_CBCInput_3TZ005.xml
>
>
> {color:#000000}There are 2 scenarios: {color}
> # XSD file is specified inside the XML file via xsi:schemaLocation attribute.
> The *"-fx"* parameter is ignored. And it causes CTAs to fail to pick up the
> full XPath 2.0
> # XSD file is specified via command line parameter *"-a"*.
> The *"-fx"* parameter is taken into the account.
> CTAs pick up the full XPath 2.0
> Here my command line statement:
> C:\Program Files\Stylus Studio X16 XML Enterprise Suite
> 64-bit\bin>*"c:\Program Files\Java\jre1.8.0_181\bin\java.exe" -Xms512m
> -Xmx1024m
> -Xbootclasspath/p:path:;c:\xerces212\xercesImpl.jar;c:\xerces212\xml-apis.jar;c:\xerces212\org.eclipse.wst.xml.xpath2.processor_1.2.0.jar;c:\xerces212\icu4j.jar;c:\xerces212\resolver.jar;c:\xerces212\serializer.jar;c:\xerces212\cupv10k-runtime.jar;c:\xerces212\xercesSamples.jar
> jaxp.SourceValidator -xsd11 -fx -i "file:///d:/Temp/Xerces-J
> 2.12.0/XercesJ_TZ20171231_IFRS15_CBCInput_3TZ005.xml"*
> It doesn't recognize the *"-fx"* parameter, and therefore, the XSD validation
> is not picking up the full XPath 2.0 for the CTAs.
> It gives the following errors:
> * [Error]IFRS15_CBC_In_XercesJ.xsd:26:185: c-cta-xpath: The XPath expression
> '@OrganizationCode = ('1GT001', '1GT005', '1GT006', '1GT010', '1HN001',
> '1HN003', '1SV001', '2BO002', '2PY003', '2PY007')' couldn't compile
> successfully in 'cta-subset' mode, during CTA evaluation.
> * [Error]IFRS15_CBC_In_XercesJ.xsd:27:89: c-cta-xpath: The XPath expression
> '@OrganizationCode eq '2CO001'' couldn't compile successfully in 'cta-subset'
> mode, during CTA evaluation.
> * [Error]IFRS15_CBC_In_XercesJ.xsd:28:99: c-cta-xpath: The XPath expression
> '@OrganizationCode = ('2CO008', '2CO009')' couldn't compile successfully in
> 'cta-subset' mode, during CTA evaluation.
> * [Error]IFRS15_CBC_In_XercesJ.xsd:29:113: c-cta-xpath: The XPath expression
> '@OrganizationCode = ('3TZ001', '3TZ002', '3TZ003', '3TZ004')' couldn't
> compile successfully in 'cta-subset' mode, during CTA evaluation.
> {color:#000000}Here my modified command line statement: {color}
> {color:#000000}C:\Program Files\Stylus Studio X16 XML Enterprise Suite
> 64-bit\bin>{color}*"c:\Program Files\Java\jre1.8.0_181\bin\java.exe" -cp
> .;c:\xerces212\* jaxp.SourceValidator -xsd11 -fx -i "file:///d:\Temp\Xerces-J
> 2.12.0\XercesJ_TZ20171231_IFRS15_CBCInput_3TZ005.xml" -a "d:\Temp\Xerces-J
> 2.12.0\IFRS15_CBC_In_XercesJ.xsd"*
> And errors are gone.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
