[ https://issues.apache.org/jira/browse/XERCESC-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ben Griffin closed XERCESC-1899.
--------------------------------
Resolution: Invalid
I have found counter examples to this.
There is something funny going on - so I will do more analysis before posting again.
> XML namespaces with more than one hyphens appear to be broken during validating parse
> -------------------------------------------------------------------------------------
>
> Key: XERCESC-1899
> URL: https://issues.apache.org/jira/browse/XERCESC-1899
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Reporter: Ben Griffin
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> This appears to cause the Parser to attempt to parse the document as a DTD document rather
than as a schema driven document.
> An example namespace causing trouble is http://www.ns.net/xxx-www-zzz
> Note that http://www.ns.net/xxx-www works fine, as does http://www.ns.net/xxx_www_zzz
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
XML namespaces with more than one hyphens appear to be broken during validating parse
-------------------------------------------------------------------------------------
Key: XERCESC-1899
URL: https://issues.apache.org/jira/browse/XERCESC-1899
Project: Xerces-C++
Issue Type: Bug
Components: Validating Parser (XML Schema)
Reporter: Ben Griffin
This appears to cause the Parser to attempt to parse the document as a DTD document rather
than as a schema driven document.
An example namespace causing trouble is http://www.ns.net/xxx-www-zzz
Note that http://www.ns.net/xxx-www works fine, as does http://www.ns.net/xxx_www_zzz
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Hi,
Xerces-C++ 3.1.0 release candidate 1 is available for download:
http://people.apache.org/builds/xerces/c/
Please test and report back any problems you find. The plan is to allow
slightly more than a month for testing and, provided no serious problems
are uncovered, release the final 3.1.0 in early January 2010.
Major new features and improvement in this release include:
* Working multi-import support. The support for handling multiple import
declarations with the same target namespaces has been improved and
thoroughly tested. Furthermore, the same logic was extended to
loadGrammar and the schemaLocation attributes so that you can load
several schemas with the same namespace and/or "add" more declarations
with the schemaLocation attributes. To enable this feature, set the
XMLUni::fgXercesHandleMultipleImports feature/parameter to true.
Starting with this release all the tests and examples have multi-import
support enabled by default.
* New property, XMLUni::fgXercesLowWaterMark, allows to configure the
parser buffer low water mark. In particular, setting this value to 0
disables data caching in the parser which can be useful if you want
the SAX events to be dispatched as soon as the data is available.
* DOMLSParser::parseWithContext implementation. In particular, this
functionality allows one to parse a document fragment with missing
namespace declarations as long as the context document provides them.
* Improved performance and reduced memory footprint when validating with
large maxOccurs values. If available, the SSE2 instructions are used to
further speedup this case.
* Improved scalability of the XML Schema identity checking (key, keyref,
and unique).
* Multiple XML Schema conformance fixes.
* More robust external library detection (libcurl and ICU). In particular,
the build system no longer tries to inject any additional paths such as
/usr or /usr/local.
* Compilation of the ICU message loader resources no longer depends on
the ICU implementation details.
The following bugs and security vulnerabilities have been fixed in this
release compared to the previous release (3.0.1):
CVE-2009-1885, XERCESC-646, XERCESC-697, XERCESC-809, XERCESC-961,
XERCESC-1021, XERCESC-1051, XERCESC-1246, XERCESC-1249, XERCESC-1263,
XERCESC-1380, XERCESC-1480, XERCESC-1481, XERCESC-1507, XERCESC-1568,
XERCESC-1583, XERCESC-1607, XERCESC-1659, XERCESC-1703, XERCESC-1707,
XERCESC-1713, XERCESC-1716, XERCESC-1717, XERCESC-1747, XERCESC-1748,
XERCESC-1759, XERCESC-1808, XERCESC-1826, XERCESC-1831, XERCESC-1833,
XERCESC-1847, XERCESC-1852, XERCESC-1856, XERCESC-1858, XERCESC-1863,
XERCESC-1866, XERCESC-1867, XERCESC-1868, XERCESC-1869, XERCESC-1870,
XERCESC-1871, XERCESC-1872, XERCESC-1874, XERCESC-1878, XERCESC-1882,
XERCESC-1892, XERCESC-1893, XERCESC-1894, XERCESC-1896 XERCESC-1898
Note to the committers: please refrain from making any changes to the
trunk except for fixing critical problems found during testing. If you
would like to continue working towards future releases, please create
a temporary branch.
Boris
--
Boris Kolpackov, Code Synthesis http://codesynthesis.com/~boris/blog
Open-source XML data binding for C++ http://codesynthesis.com/products/xsd
XML data binding for embedded systems http://codesynthesis.com/products/xsde
Command line interface to C++ compiler http://codesynthesis.com/projects/cli
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Hi, I am unable to build xerces 2.6.0 in 64-bit mode on SPARC and x86 platform. I have used "./runConfigure -p solaris -c cc -x CC " to configure 32-bit on SPARC using sunstudio compiler to build. That works fine. However I am not sure why 64-bit doesn't work. For SPARC, I tried following options in runConfigure, which returned an ELF class error during link time. ./runConfigure -p solaris -c cc -x CC -l -xarch=v9 ld: fatal: file SOLARIS/ASCIIRangeFactory.o: wrong ELF class: ELFCLASS32 ld: fatal: File processing errors. No output written to /home/vn125969/xerces/xe rces-c-src_2_6_0/lib/libxerces-c.so.26.0 gmake[1]: *** [/home/vn125969/xerces/xerces-c-src_2_6_0/lib/libxerces-c.so.26.0] Error 1 same with the Solaris X86 build as well. What is missing in the above approach. Kindly help. Thanks, Vinu --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781187#action_12781187
]
David Bertoni commented on XERCESC-1368:
----------------------------------------
This is not a problem with Visual Studio 2005 and later, so perhaps it's not worth doing any
more work to fix it.
> Catch-all handler are problematic on Windows
> --------------------------------------------
>
> Key: XERCESC-1368
> URL: https://issues.apache.org/jira/browse/XERCESC-1368
> Project: Xerces-C++
> Issue Type: Bug
> Components: Miscellaneous
> Affects Versions: 3.0.1
> Environment: Windows XP with Visual Studio .NET 2003
> Reporter: David Bertoni
> Assignee: David Bertoni
> Attachments: patch.txt
>
>
> Exception handlers of the form "catch(...)" are causing problems in our product code
on Windows, because they are catching hardware exceptions, such as access violations.
> There is an article in the MSDN Knowledge Base that describes how this has changed between
Visual Studio 6, and Visual Studio .NET:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclang/html/_core_exception_handling.3a_.default_synchronous_exception_model.asp
> However, my experience with Xerces-C using Visual Studio .NET 2003 is that hardware exceptions
(asynchronous exceptions, in the Microsoft parlance) are still being caught in Xerces-C in
catch-all handlers. This is problematic because it interferes with normal diagnosis of hardware
faults, and can lead to code being executed in Xerces-C when the system is in an unknown state.
It is also a makes it difficult to write code that will behave the same on other platforms.
> Looking into the code reveals multiple places where a catch-all handler resets some object
(or some other similar behavior), then rethrows the same exception. I'd like to propose that
we try to eliminate as many of these catch handlers as possible by replaces these actions
with stack objects that perform these actions automatically whether or not an exception is
thrown (auto_ptr-like behavior). This will also have the benefit of simplifying the code.
From a "philosophical" perspective, I also think its better for code to catch the exceptions
it's concerned with, and avoid catch-all handlers except when absolutely necessary.
> I will attach a proposed patch for a class that does this sort of thing, and some modified
code that uses this class. I would also like to see if anyone else has observed this behavior
in their Windows applications.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781186#action_12781186
]
David Bertoni commented on XERCESC-1866:
----------------------------------------
Sorry, I've been traveling for work, and haven't been able to to much for the last month.
Yes, this is a temporary fix, but the permanent fix will break binary and API compatibility,
so it will need to wait.
> Crash with regular expression
> -----------------------------
>
> Key: XERCESC-1866
> URL: https://issues.apache.org/jira/browse/XERCESC-1866
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Environment: Windows XP, Visual Studio 2005
> Reporter: Alexander Hartmann
> Assignee: David Bertoni
> Fix For: 3.2.0, 4.0.0
>
> Attachments: XERCESC-1866.patch
>
>
> when I run the following test code my application crashes on the second regEx.matches
call:
> {
> XMLBuffer optionsBuf;
> optionsBuf.append('i');
> optionsBuf.append('H');
> RegularExpression regEx(L"^\\W*Excel\\W*$", optionsBuf.getRawBuffer());
> regEx.matches("Excel");
> }
> {
> XMLBuffer optionsBuf;
> optionsBuf.append('i');
> optionsBuf.append('H');
> RegularExpression regEx(L"^\\W*Excel\\W*$", optionsBuf.getRawBuffer());
> regEx.matches("Excel");
> }
> some details I found during debugging:
> - there is an instance of RangeToken where I have no idea where this is created. I've
set a breakpoint in the constructor but the debugger does not stop.
> - when RangeToken::getCaseInsensitiveToken is called a new RangeToken is created and
stored in fCaseIToken
> - when parsing is finished the newly created RangeToken is deleted (through ~RegularExpression
-> ~TokenFactory), but the original RangeToken (where I don't know where it is created)
still exists and references the deleted RangeToken in fCaseIToken
> - the next time RangeToken::getCaseInsensitiveToken is called the invalid reference fCaseIToken
is returned and this leads to a crash when it is accessed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1881:
-------------------------------------
Fix Version/s: (was: 3.1.0)
4.0.0
3.2.0
Rescheduling to 3.2.0/4.0.0.
> xsd sequence validation reporting errors too late
> -------------------------------------------------
>
> Key: XERCESC-1881
> URL: https://issues.apache.org/jira/browse/XERCESC-1881
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.0.1
> Environment: Windows Visaa 32, Xerces 3.0.1
> Reporter: Brian Hoyt
> Fix For: 3.2.0, 4.0.0
>
>
> Validation using the following xsd and xml results in two different results between XercesJ
and XercesC++.
> For java I get the error reporting the sequence error right after the processing of element
<url> because <name>
> cannot appear after <url>. But for C++ the error is not reported until the last
element within <person> has been
> processed. This obviously isn't correct because by that time it is too late. The way
Java is reporting it seems to
> be correct so that I can stop processing the xml file.
> <?xml version="1.0" encoding="UTF-8"?>
> <xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'>
> <xs:element name="person">
> <xs:complexType>
> <xs:sequence>
> <xs:element name="name" type='xs:string' minOccurs='0' maxOccurs='1'/>
> <xs:element name="email" type='xs:string' minOccurs='0' maxOccurs='unbounded'/>
> <xs:element name="url" type='xs:string' minOccurs='0' maxOccurs='unbounded'/>
> <xs:element name="link" type='xs:string' minOccurs='0' maxOccurs='1'/>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> </xs:schema>
> <?xml version="1.0" encoding="UTF-8"?>
> <person xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation='foo.xsd'>
> <url>www.foo.com</url>
> <name>Boss</name>
> <email>chief@foo.com</email>
> <link/>
> </person>
> The output from running the XercesJ 2.9.1 Writer sample on the above xsd/xml is:
> <person xsi:noNamespaceSchemaLocation="foo.xsd">
> <url>www.foo.com</url>
> [Error] foo.xml:5:11: cvc-complex-type.2.4.a: Invalid content was found star
> ting with element 'name'. One of '{url, link}' is expected.
> <name>Boss</name>
> <email>chief@foo.com</email>
> <link></link>
> </person>
> The output from running the XercesC++ 3.0.1
> <?xml version="1.0" encoding="LATIN1"?>
> <person xsi:noNamespaceSchemaLocation="foo.xsd">
> <url>www.foo.com</url>
> <name>Boss</name>
> <email>chief@foo.com</email>
> <link></link>
> Error at file C:\xerces-3_0_1\bin/foo.xml, line 8, char 10
> Message: element 'name' is not allowed for content model '((name,email,url),li
> nk)'
> </person>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Let's start from scratch: 1) download http://archive.apache.org/dist/xml/xerces-c/Xerces-C_2_6_0/xerces-c-src_2_6_0.zip 2) unzip to a new folder 3) start VC6, open <xerces>/Projects/Win32/VC6/xerces-all/xerces-all.dsw 4) click on the Build menu, select Batch Build then click Rebuild All Alberto Vinutha Nagaraju wrote: > Alberto Massari wrote: >> xerces-c_2.lib and xerces-depdom_2.lib are the Release builds; in >> order to select the release build you can use the combo box in the >> toolbar. If you don't see it, right click on the toolbar area and >> select it from the list (usually it's the mini-build toolbar that is >> displayed, the one with just the buttons to start the build) >> > I have attached the screen shot of my workspace. I used the mini tool > bar as u suggested even then, it doesn't work. > Basically in the output window, it says no configuration specified > hence defaulting to debug build. > > When I loaded the Xerceslib.dsp, there was warning that this project > wasn't built using Developer studio, so it would create another > Makefile as a wrapper to the existing one. Not sure because of that it > if something is wrong. I see that after building the debug bits, there > three new files created. > 1. xerceslib.opt > 2. xerceslib.dsw > 3. xerceslib1.dsp > 4. xerceslib1.plg > Is there a way I could edit the Makefile manually to build release > bits by default ? > > THanks, > Vinu > > >> Alberto >> >> Vinutha Nagaraju wrote: >>> Thanks for the quick response. >>> I am not able to build the release version. >>> In MSVC, under Build tab, I selected "Set Active Configuration" to >>> "Release". But it still builds debug version. >>> any clue ? >>> One more question, In the past someone else in my team had built >>> windows and in his workspace I see two extra libraries >>> "xerces-c_2.lib" and "xerces-depdom_2.lib". This is missing in my >>> workspace, I only have xerces-c_2D.lib and Xerces-depdom_2D.lib. >>> Are these release and debug bits by any chance ? >>> >>> Thanks, >>> Vinu >>> >>> >>> Alberto Massari wrote: >>>> That's the "debug" folder; you should also select the "Release" >>>> configuration, and build it. The output for that configuration will >>>> be in the Build/VC6/Release folder. >>>> Also, if you use the deprecated DOM, you should select the >>>> DeprecatedDOM project, right click to get the popup menu, and >>>> choose Build >>>> >>>> Alberto >>>> >>>> Vinutha Nagaraju wrote: >>>>> >>>>> Hi, >>>>> >>>>> I have a query on building Xerces 2.6.0 on Windows. >>>>> I have followed the instructions provided in Readme.html. I have >>>>> opened the Project >>>>> >>>>> Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw >>>>> >>>>> in MSVC6.0. Then built Xerceslib. Though I haven't seen any build >>>>> errors, I am not sure if the final bits created is what is expected. >>>>> >>>>> I see the following files created in Build/Win32/VC6/Debug/ >>>>> -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib >>>>> -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp >>>>> -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 >>>>> xerces-c_2_6D.pdb >>>>> -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 >>>>> xerces-c_2_6D.ilk >>>>> -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 >>>>> xerces-c_2_6D.dll >>>>> >>>>> Can someone please confirm if the above files are windows >>>>> expected files ? If not, what is missing and how to built it ? >>>>> >>>>> Thanks, >>>>> Vinu >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >>>> For additional commands, e-mail: c-dev-help@xerces.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >>> For additional commands, e-mail: c-dev-help@xerces.apache.org >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >> For additional commands, e-mail: c-dev-help@xerces.apache.org >> > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org > For additional commands, e-mail: c-dev-help@xerces.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
I think I could resolve it. I manually ran nmake with CFG pointing to release. That seems to go through now. Thanks a lot for all the comments provided so far. regards, Vinu Vinutha Nagaraju wrote: > Alberto Massari wrote: >> xerces-c_2.lib and xerces-depdom_2.lib are the Release builds; in >> order to select the release build you can use the combo box in the >> toolbar. If you don't see it, right click on the toolbar area and >> select it from the list (usually it's the mini-build toolbar that is >> displayed, the one with just the buttons to start the build) >> > I have attached the screen shot of my workspace. I used the mini tool > bar as u suggested even then, it doesn't work. > Basically in the output window, it says no configuration specified > hence defaulting to debug build. > > When I loaded the Xerceslib.dsp, there was warning that this project > wasn't built using Developer studio, so it would create another > Makefile as a wrapper to the existing one. Not sure because of that it > if something is wrong. I see that after building the debug bits, there > three new files created. > 1. xerceslib.opt > 2. xerceslib.dsw > 3. xerceslib1.dsp > 4. xerceslib1.plg > Is there a way I could edit the Makefile manually to build release > bits by default ? > > THanks, > Vinu > > >> Alberto >> >> Vinutha Nagaraju wrote: >>> Thanks for the quick response. >>> I am not able to build the release version. >>> In MSVC, under Build tab, I selected "Set Active Configuration" to >>> "Release". But it still builds debug version. >>> any clue ? >>> One more question, In the past someone else in my team had built >>> windows and in his workspace I see two extra libraries >>> "xerces-c_2.lib" and "xerces-depdom_2.lib". This is missing in my >>> workspace, I only have xerces-c_2D.lib and Xerces-depdom_2D.lib. >>> Are these release and debug bits by any chance ? >>> >>> Thanks, >>> Vinu >>> >>> >>> Alberto Massari wrote: >>>> That's the "debug" folder; you should also select the "Release" >>>> configuration, and build it. The output for that configuration will >>>> be in the Build/VC6/Release folder. >>>> Also, if you use the deprecated DOM, you should select the >>>> DeprecatedDOM project, right click to get the popup menu, and >>>> choose Build >>>> >>>> Alberto >>>> >>>> Vinutha Nagaraju wrote: >>>>> >>>>> Hi, >>>>> >>>>> I have a query on building Xerces 2.6.0 on Windows. >>>>> I have followed the instructions provided in Readme.html. I have >>>>> opened the Project >>>>> >>>>> Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw >>>>> >>>>> in MSVC6.0. Then built Xerceslib. Though I haven't seen any build >>>>> errors, I am not sure if the final bits created is what is expected. >>>>> >>>>> I see the following files created in Build/Win32/VC6/Debug/ >>>>> -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib >>>>> -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp >>>>> -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 >>>>> xerces-c_2_6D.pdb >>>>> -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 >>>>> xerces-c_2_6D.ilk >>>>> -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 >>>>> xerces-c_2_6D.dll >>>>> >>>>> Can someone please confirm if the above files are windows >>>>> expected files ? If not, what is missing and how to built it ? >>>>> >>>>> Thanks, >>>>> Vinu >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >>>> For additional commands, e-mail: c-dev-help@xerces.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >>> For additional commands, e-mail: c-dev-help@xerces.apache.org >>> >>> > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT Alberto Massari wrote: > xerces-c_2.lib and xerces-depdom_2.lib are the Release builds; in > order to select the release build you can use the combo box in the > toolbar. If you don't see it, right click on the toolbar area and > select it from the list (usually it's the mini-build toolbar that is > displayed, the one with just the buttons to start the build) > I have attached the screen shot of my workspace. I used the mini tool bar as u suggested even then, it doesn't work. Basically in the output window, it says no configuration specified hence defaulting to debug build. When I loaded the Xerceslib.dsp, there was warning that this project wasn't built using Developer studio, so it would create another Makefile as a wrapper to the existing one. Not sure because of that it if something is wrong. I see that after building the debug bits, there three new files created. 1. xerceslib.opt 2. xerceslib.dsw 3. xerceslib1.dsp 4. xerceslib1.plg Is there a way I could edit the Makefile manually to build release bits by default ? THanks, Vinu > Alberto > > Vinutha Nagaraju wrote: >> Thanks for the quick response. >> I am not able to build the release version. >> In MSVC, under Build tab, I selected "Set Active Configuration" to >> "Release". But it still builds debug version. >> any clue ? >> One more question, In the past someone else in my team had built >> windows and in his workspace I see two extra libraries >> "xerces-c_2.lib" and "xerces-depdom_2.lib". This is missing in my >> workspace, I only have xerces-c_2D.lib and Xerces-depdom_2D.lib. >> Are these release and debug bits by any chance ? >> >> Thanks, >> Vinu >> >> >> Alberto Massari wrote: >>> That's the "debug" folder; you should also select the "Release" >>> configuration, and build it. The output for that configuration will >>> be in the Build/VC6/Release folder. >>> Also, if you use the deprecated DOM, you should select the >>> DeprecatedDOM project, right click to get the popup menu, and choose >>> Build >>> >>> Alberto >>> >>> Vinutha Nagaraju wrote: >>>> >>>> Hi, >>>> >>>> I have a query on building Xerces 2.6.0 on Windows. >>>> I have followed the instructions provided in Readme.html. I have >>>> opened the Project >>>> >>>> Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw >>>> >>>> in MSVC6.0. Then built Xerceslib. Though I haven't seen any build >>>> errors, I am not sure if the final bits created is what is expected. >>>> >>>> I see the following files created in Build/Win32/VC6/Debug/ >>>> -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib >>>> -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp >>>> -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 >>>> xerces-c_2_6D.pdb >>>> -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 >>>> xerces-c_2_6D.ilk >>>> -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 >>>> xerces-c_2_6D.dll >>>> >>>> Can someone please confirm if the above files are windows expected >>>> files ? If not, what is missing and how to built it ? >>>> >>>> Thanks, >>>> Vinu >>>> >>>> >>>> >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >>> For additional commands, e-mail: c-dev-help@xerces.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >> For additional commands, e-mail: c-dev-help@xerces.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org > For additional commands, e-mail: c-dev-help@xerces.apache.org >
xerces-c_2.lib and xerces-depdom_2.lib are the Release builds; in order to select the release build you can use the combo box in the toolbar. If you don't see it, right click on the toolbar area and select it from the list (usually it's the mini-build toolbar that is displayed, the one with just the buttons to start the build) Alberto Vinutha Nagaraju wrote: > Thanks for the quick response. > I am not able to build the release version. > In MSVC, under Build tab, I selected "Set Active Configuration" to > "Release". But it still builds debug version. > any clue ? > One more question, In the past someone else in my team had built > windows and in his workspace I see two extra libraries > "xerces-c_2.lib" and "xerces-depdom_2.lib". This is missing in my > workspace, I only have xerces-c_2D.lib and Xerces-depdom_2D.lib. > Are these release and debug bits by any chance ? > > Thanks, > Vinu > > > Alberto Massari wrote: >> That's the "debug" folder; you should also select the "Release" >> configuration, and build it. The output for that configuration will >> be in the Build/VC6/Release folder. >> Also, if you use the deprecated DOM, you should select the >> DeprecatedDOM project, right click to get the popup menu, and choose >> Build >> >> Alberto >> >> Vinutha Nagaraju wrote: >>> >>> Hi, >>> >>> I have a query on building Xerces 2.6.0 on Windows. >>> I have followed the instructions provided in Readme.html. I have >>> opened the Project >>> >>> Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw >>> >>> in MSVC6.0. Then built Xerceslib. Though I haven't seen any build >>> errors, I am not sure if the final bits created is what is expected. >>> >>> I see the following files created in Build/Win32/VC6/Debug/ >>> -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib >>> -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp >>> -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 xerces-c_2_6D.pdb >>> -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 >>> xerces-c_2_6D.ilk >>> -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 xerces-c_2_6D.dll >>> >>> Can someone please confirm if the above files are windows expected >>> files ? If not, what is missing and how to built it ? >>> >>> Thanks, >>> Vinu >>> >>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org >> For additional commands, e-mail: c-dev-help@xerces.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org > For additional commands, e-mail: c-dev-help@xerces.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
Thanks for the quick response. I am not able to build the release version. In MSVC, under Build tab, I selected "Set Active Configuration" to "Release". But it still builds debug version. any clue ? One more question, In the past someone else in my team had built windows and in his workspace I see two extra libraries "xerces-c_2.lib" and "xerces-depdom_2.lib". This is missing in my workspace, I only have xerces-c_2D.lib and Xerces-depdom_2D.lib. Are these release and debug bits by any chance ? Thanks, Vinu Alberto Massari wrote: > That's the "debug" folder; you should also select the "Release" > configuration, and build it. The output for that configuration will be > in the Build/VC6/Release folder. > Also, if you use the deprecated DOM, you should select the > DeprecatedDOM project, right click to get the popup menu, and choose > Build > > Alberto > > Vinutha Nagaraju wrote: >> >> Hi, >> >> I have a query on building Xerces 2.6.0 on Windows. >> I have followed the instructions provided in Readme.html. I have >> opened the Project >> >> Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw >> >> in MSVC6.0. Then built Xerceslib. Though I haven't seen any build >> errors, I am not sure if the final bits created is what is expected. >> >> I see the following files created in Build/Win32/VC6/Debug/ >> -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib >> -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp >> -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 xerces-c_2_6D.pdb >> -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 xerces-c_2_6D.ilk >> -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 xerces-c_2_6D.dll >> >> Can someone please confirm if the above files are windows expected >> files ? If not, what is missing and how to built it ? >> >> Thanks, >> Vinu >> >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org > For additional commands, e-mail: c-dev-help@xerces.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
That's the "debug" folder; you should also select the "Release" configuration, and build it. The output for that configuration will be in the Build/VC6/Release folder. Also, if you use the deprecated DOM, you should select the DeprecatedDOM project, right click to get the popup menu, and choose Build Alberto Vinutha Nagaraju wrote: > > Hi, > > I have a query on building Xerces 2.6.0 on Windows. > I have followed the instructions provided in Readme.html. I have > opened the Project > > Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw > > in MSVC6.0. Then built Xerceslib. Though I haven't seen any build > errors, I am not sure if the final bits created is what is expected. > > I see the following files created in Build/Win32/VC6/Debug/ > -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib > -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp > -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 xerces-c_2_6D.pdb > -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 xerces-c_2_6D.ilk > -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 xerces-c_2_6D.dll > > Can someone please confirm if the above files are windows expected > files ? If not, what is missing and how to built it ? > > Thanks, > Vinu > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
Hi, I have a query on building Xerces 2.6.0 on Windows. I have followed the instructions provided in Readme.html. I have opened the Project Projects\Win32\VC6\xerces-all\XercesLib\XercesLib.dsw in MSVC6.0. Then built Xerceslib. Though I haven't seen any build errors, I am not sure if the final bits created is what is expected. I see the following files created in Build/Win32/VC6/Debug/ -rwxr-xr-x 1 nobody nobody 2977668 Nov 17 13:24 xerces-c_2D.lib -rwxr-xr-x 1 nobody nobody 1820661 Nov 17 13:24 xerces-c_2D.exp -rwxr-xr-x 1 nobody nobody 4719616 Nov 17 13:24 xerces-c_2_6D.pdb -rwxr-xr-x 1 nobody nobody 21348168 Nov 17 13:24 xerces-c_2_6D.ilk -rwxr-xr-x 1 nobody nobody 3219545 Nov 17 13:24 xerces-c_2_6D.dll Can someone please confirm if the above files are windows expected files ? If not, what is missing and how to built it ? Thanks, Vinu --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1659.
------------------------------------
Resolution: Fixed
The fix is in SVN. All test cases now pass with multi-import support enabled.
> Order sensitivity in schemaLocation and noNamespaceSchemaLocation
> -----------------------------------------------------------------
>
> Key: XERCESC-1659
> URL: https://issues.apache.org/jira/browse/XERCESC-1659
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: all
> Reporter: Boris Kolpackov
> Assignee: Boris Kolpackov
> Fix For: 3.1.0
>
> Attachments: test-case-1.tar.gz, test-case-2.tar.gz
>
>
> I am attaching two test cases (each consists of 3 schemas plus an XML instance). If you
try to run domprint on the first test case, you will get the following error:
> $ domprint -v=always -n -s -f test-users.xml
> Error at file "test-users.xml", line 6, column 78
> Message: Unknown element 'b:UserDatabase'
> If you change the order of the schemaLocation and noNamespaceSchemaLocation attributes
in test-users.xml then the error disappears.
> The second test case is a slight modification of the first test case with the only difference
being the schemas with targetNamespace are now do not have a namespace, and the schema that
used to be without a namespace (derived-user-config.xsd) now is in a namespace. If you run
domprint on this test case, you will get the following error:
> $ domprint -v=always -n -s -f test-users.xml
> Error at file "test-users.xml", line 6, column 55
> Message: Unknown element 'UserDatabase'
> This seems to prove that for Xerces-C++, for some reason, it is important that the schema
that declares the root element is mentioned in the first *Location attribute (nor matter whether
schemaLocation or noNamespaceSchemaLocation). Now comes the surprise: if we reverse the order
of the two attributes in the second test case, domprint terminates with segmentation fault.
Examination of the core points to the IGXMLScanner.cpp, line 2288:
> elemDecl = fGrammar->getElemDecl(
> uriId, nameRawBuf, qnameRawBuf, currentScope
> );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779522#action_12779522
]
Vit Ondruch commented on XERCESC-1587:
--------------------------------------
Works also for me in 2.8.0 which I am currently using.
> The default values for attributes in schema are not resolved using DOMBuilder
> -----------------------------------------------------------------------------
>
> Key: XERCESC-1587
> URL: https://issues.apache.org/jira/browse/XERCESC-1587
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.6.0
> Reporter: Vit Ondruch
>
> I was used to use the XSD schema with default attribute values as:
> <xs:attribute name="MaxSequenceLength" type="xs:unsignedLong" form="unqualified" default="1"
/>
> A lot of my XML files does not contained the attributes with specified default value
at all. When i used the XercesDOMParser, everything worked as expected and when i try to retrieve
the value of such attribute, the default value was returned, but that does not apply for DOMBuilder
unfortunatelly. The attribute is simply not found, which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1263.
------------------------------------
Resolution: Fixed
Assignee: Boris Kolpackov
The fix is in SVN.
> Abstract type not handled correctly by cached grammar
> -----------------------------------------------------
>
> Key: XERCESC-1263
> URL: https://issues.apache.org/jira/browse/XERCESC-1263
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Reporter: Matthew Berry
> Assignee: Boris Kolpackov
> Fix For: 3.1.0
>
>
> Details:
> --------
> I have managed to narrow the problem I am having to a simple test case. In the schema,
I have an abstract type defined and am using xsi:type with a concrete type in the data file.
> If I have a xsi:schemaLocation attribute in my data file, then the test Xml file passes
the validation. (I have used DOMCount to verify this)
> If I remove xsi:schemaLocation and instead from my source code call loadGrammar() and
setFeature(XMLUni::fgXercesUseCachedGrammarInParse, true), I am getting the following error
messages:
> Message: Element paramInstance is declared with a type that is
> abstract. Use xsi:type to specify a non-abstract type
> Message: Attribute 'name' is not declared for
> element 'paramInstance'
> Schema:
> -------
> <xsd:schema targetNamespace="http://www.temp.org" xmlns:tmp="http://www.temp.org"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <!--
> Define a 'paramInstance' element
> NOTE: We use an abstract base to allow for extension
> -->
> <xsd:complexType name="ParamInstanceType" abstract="true" />
> <xsd:element name="paramInstance" type="ParamInstanceType" />
> <!--
> Specifying a concrete type
> -->
> <xsd:complexType name="ConcreteParamInstance">
> <xsd:complexContent>
> <xsd:extension base="tmp:ParamInstanceType">
> <xsd:attribute name="name" type="xsd:string" use="required" />
> </xsd:extension>
> </xsd:complexContent>
> </xsd:complexType>
> </xsd:schema>
> Test data file:
> ---------------
> <paramInstance xmlns="http://www.temp.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:type="ConcreteParamInstance" name="param1" />
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
If I understand you correctly, what I described is not in fact exactly what you do. It sounds like rather than the invalid serialization that I asked about, your document is being serialized correctly. Invalid: <editnumber formula="<data>.//activity/@status</data>"/> Valid: <editnumber formula="<data>.//activity/@status</data>"/> If this is true, the problem is in the parsing as you suggest. I think a test case is needed. I'd recommend attaching an example of a problematic document that cannot be processed by one of the sample applications (like DOMParse). -----Original Message----- From: Leif Goodwin [mailto:lgoodwin@qgsl.com] Sent: Wednesday, November 18, 2009 5:31 AM To: c-dev@xerces.apache.org Subject: RE: How to have an attribute which contains XML Yes, that is exactly what we do. I use the setAttribute method on DOMElement instance passing name as "formula" and value as "<data>.//activity/@status</data>". Then I serialise the DOMDocument to a string. When I examine the string, I see that Xerces has replaced each '<' with "<" which is correct. But it leaves each '>' as is. Then when I try to serialise the string into a DOM document, the result is nonsense, as I think the '>' characters are interpreted as close element markers. I tried replacing each '>' with ">" in the string before passing it to setAttribute, but that did not work, as it replces the '&' with "&". --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1703.
------------------------------------
Resolution: Fixed
Assignee: Boris Kolpackov
The fix is in SVN.
> Bad error description reported by xerces
> ----------------------------------------
>
> Key: XERCESC-1703
> URL: https://issues.apache.org/jira/browse/XERCESC-1703
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: all platforms
> Reporter: Anton Nikolaevsky
> Assignee: Boris Kolpackov
> Fix For: 3.1.0
>
>
> xml:
> <date/>
> xsd:
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="date" type="xsd:dateTime"/>
> </xsd:schema>
> Observed: error "Datatype error: Type:SchemaDateTimeException, Message:buffer not initialized
> yet!."
> Expected error message: something like " '' is not a valid value for the type {http://www.w3.org/2001/XMLSchema}dateTime"
> An exception is thrown at XMLDateTime.hpp[411] from XMLDateTime::assertBuffer() invoked
by XMLDateTime::initParser().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1826.
------------------------------------
Resolution: Fixed
The fix is in SVN.
> XMLURL::makeNewStream() fails to decode file:/// URLs containing the (properly escaped)
% character
> ---------------------------------------------------------------------------------------------------
>
> Key: XERCESC-1826
> URL: https://issues.apache.org/jira/browse/XERCESC-1826
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Affects Versions: 2.5.0, 2.6.0, 2.7.0, 2.8.0, 3.0.0, 2.9.0, 3.1.0
> Environment: Windows XP Prof. German, MS Visual Studio 2003
> Reporter: Matteo Ceruti
> Assignee: Boris Kolpackov
> Fix For: 3.1.0
>
>
> I truly believe that XMLURL::makeNewStream() (see src/xercesc/util/XMLURL.cpp) does not
correctly handle file:///-URLs containing the escape-sequence %25 (that is the '%'-character
itself). Consider you have a win32 filepath like "C:\Documents\myfile_%_.xml" . Its URL would
be "file:///C:/Documents/myfile_%25_.xml", right? But this URL is rejected by raising a MalformedURLException.
> makeNewStream() decodes the URL by searching and replacing the escape-sequences one by
one. When it sucessfully replaced %25 by the '%'-character it continunes it's search for the
next escape-sequence. The problem is, that it starts at the very position, where the last
escape-sequence began. Therefore it suddenly finds a %-character again, because it had just
been put there.
> This happens at least with xerces-c 2.5 and it seems that the current (revision=670359)
http://svn.apache.org/viewvc/xerces/c/trunk/src/xercesc/util/XMLURL.cpp still has this problem.
So probably other releases may have the same issue.
> I think the line
> percentIndex = XMLString::indexOf(realPath, chPercent, percentIndex, fMemoryManager);
> should be replaced by
> percentIndex = XMLString::indexOf(realPath, chPercent, percentIndex + 1, fMemoryManager);
> This works for me.
> Please correct me, if I'm wrong. Thank you in advance.
> Best regards,
> Matteo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1800:
-------------------------------------
Affects Version/s: (was: 3.0.0)
3.1.0
Fix Version/s: (was: 3.1.0)
4.0.0
3.2.0
Rescheduling for 3.2.0/4.0.0.
> Xerces-C++ is not 64-bit safe
> -----------------------------
>
> Key: XERCESC-1800
> URL: https://issues.apache.org/jira/browse/XERCESC-1800
> Project: Xerces-C++
> Issue Type: Bug
> Components: Build
> Affects Versions: 3.1.0
> Reporter: Boris Kolpackov
> Priority: Critical
> Fix For: 3.2.0, 4.0.0
>
>
> There are a number of places in DOM where unsigned int and unsigned long are used for
indexes and sizes. These should be changed to XMLSize_t. Here is the grep result:
> DOMDocument.hpp: const unsigned long
lineNum,
> DOMDocument.hpp: const unsigned long
columnNum) = 0;
> DOMDocumentTraversal.hpp: unsigned
long whatToShow,
> DOMDocumentTraversal.hpp: unsigned long
whatToShow,
> DOMLocator.hpp: virtual unsigned long getLineNumber() const = 0;
> DOMLocator.hpp: virtual unsigned long getColumnNumber() const = 0;
> DOMLSParserFilter.hpp: virtual unsigned long getWhatToShow() const = 0;
> DOMLSSerializerFilter.hpp: virtual unsigned long getWhatToShow() const =0;
> DOMLSSerializerFilter.hpp: // unsigned long fWhatToShow;
> DOMNodeIterator.hpp: virtual unsigned long getWhatToShow() = 0;
> DOMTreeWalker.hpp: virtual unsigned long getWhatToShow()= 0;
> DOMTypeInfo.hpp: virtual bool isDerivedFrom(const XMLCh* typeNamespaceArg, const XMLCh*
typeNameArg, unsigned long derivationMethod) const = 0;
> DOMXPathResult.hpp: virtual unsigned long getSnapshotLength() const = 0;
> DOMXPathResult.hpp: * @param index of type unsigned long - Index into the snapshot
collection.
> DOMXPathResult.hpp: virtual const DOMNode* snapshotItem(unsigned long index) const
= 0;
> DOMImplementationList.hpp: virtual DOMImplementation *item(unsigned int index) const
= 0;
> DOMImplementationList.hpp: virtual unsigned int getLength() const = 0;
> DOMLSParser.hpp: virtual const XMLCh* getURIText(unsigned int uriId) const = 0;
> DOMNamedNodeMap.hpp: virtual DOMNode *item(unsigned int index) const = 0;
> DOMNamedNodeMap.hpp: virtual unsigned int getLength() const = 0;
> DOMNodeList.hpp: virtual DOMNode *item(unsigned int index) const = 0;
> DOMNodeList.hpp: virtual unsigned int getLength() const = 0;
> DOMStringList.hpp: virtual const XMLCh *item(unsigned int index) const = 0;
> DOMStringList.hpp: virtual unsigned int getLength() const = 0;
> Ideally, we should do such an audit of the entire codebase.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1854:
-------------------------------------
Fix Version/s: (was: 3.1.0)
4.0.0
3.2.0
Rescheduling for 3.2.0/4.0.0.
> Serialization does not detect invalid XML characters
> ----------------------------------------------------
>
> Key: XERCESC-1854
> URL: https://issues.apache.org/jira/browse/XERCESC-1854
> Project: Xerces-C++
> Issue Type: Bug
> Components: DOM
> Affects Versions: 3.0.1
> Reporter: Boris Kolpackov
> Fix For: 3.2.0, 4.0.0
>
> Attachments: test.cxx
>
>
> The attached test case serializes an invalid XML 1.0 document that contains a character
with value 0x04. See http://www.w3.org/TR/REC-xml/#NT-Char for the list of valid characters
in an XML 1.0 document.
> I've done some digging and it seems that XMLFormatter should check for this. In fast,
there is already code for XML 1.1 that checks for these control characters since they need
to be escaped in 1.1. It looks like we need to check for invalid characters when in the 1.0
mode. There is the XMLChar1_0::isXMLChar() function which can presumably be used.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
Yes, that is exactly what we do. I use the setAttribute method on DOMElement instance passing name as "formula" and value as "<data>.//activity/@status</data>". Then I serialise the DOMDocument to a string. When I examine the string, I see that Xerces has replaced each '<' with "<" which is correct. But it leaves each '>' as is. Then when I try to serialise the string into a DOM document, the result is nonsense, as I think the '>' characters are interpreted as close element markers. I tried replacing each '>' with ">" in the string before passing it to setAttribute, but that did not work, as it replces the '&' with "&". Are you saying that the document may be serialized with an element like the following? <editnumber formula="<data>.//activity/@status</data>"> If so, the serialization is invalid. See http://www.w3.org/TR/2006/REC-xml-20060816/#syntax. '<' must be represented as a numeric character reference or '<' when it's not used as a markup delimiter. If humans have to look at the markup, you might want to represent '>' as '>' for symmetry. Note that ampersands must also be escaped. A spec-compliant XML processor will take care of this for you. -- View this message in context: http://old.nabble.com/How-to-have-an-attribute-which-contains-XML-tp26392607p26405545.html Sent from the Xerces - C - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1748.
------------------------------------
Resolution: Fixed
The fix is in SVN.
> parsing registry based authorities in URI fails
> -----------------------------------------------
>
> Key: XERCESC-1748
> URL: https://issues.apache.org/jira/browse/XERCESC-1748
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.0.1
> Environment: Linux
> Reporter: G. Kramer
> Assignee: Boris Kolpackov
> Priority: Blocker
> Fix For: 3.1.0
>
> Attachments: anyURITest.xml, anyURITest.xsd, xercesc-1748patch.txt
>
>
> validating documents against schema containing registry based authorities in anyURI typed
attributes fails with:
> Message: Datatype error: Type:InvalidDatatypeValueException, Message:Value '...' is NOT
a valid URI
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1747.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
The fix is in SVN.
> Schema validation fails on cpe schema
> -------------------------------------
>
> Key: XERCESC-1747
> URL: https://issues.apache.org/jira/browse/XERCESC-1747
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.7.0
> Environment: windows, linux, osx, solaris
> Reporter: Paul Whitehurst
> Fix For: 3.1.0
>
> Attachments: cpe-1.0.xsd, cpetest.xml
>
>
> Xerces C fails to validate against the CPE schema (http://cpe.mitre.org/) with an invalid
URI error.
> Using the PParse test application I get the following error:
> Error at file C:\dev\test\schema\cpetest.xml, line 4, char 60
> Message: Datatype error: Type:InvalidDatatypeValueException, Message:Value 'cpe://microsoft.windows:vista'
is NOT a valid URI .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1866:
-------------------------------------
Fix Version/s: (was: 3.1.0)
4.0.0
3.2.0
I have committed the attached patch for 3.1.0. I am leaving this bug open and rescheduling
it for 3.2.0/4.0.0 since this seems to be a temporary fix.
> Crash with regular expression
> -----------------------------
>
> Key: XERCESC-1866
> URL: https://issues.apache.org/jira/browse/XERCESC-1866
> Project: Xerces-C++
> Issue Type: Bug
> Components: Utilities
> Environment: Windows XP, Visual Studio 2005
> Reporter: Alexander Hartmann
> Assignee: David Bertoni
> Fix For: 3.2.0, 4.0.0
>
> Attachments: XERCESC-1866.patch
>
>
> when I run the following test code my application crashes on the second regEx.matches
call:
> {
> XMLBuffer optionsBuf;
> optionsBuf.append('i');
> optionsBuf.append('H');
> RegularExpression regEx(L"^\\W*Excel\\W*$", optionsBuf.getRawBuffer());
> regEx.matches("Excel");
> }
> {
> XMLBuffer optionsBuf;
> optionsBuf.append('i');
> optionsBuf.append('H');
> RegularExpression regEx(L"^\\W*Excel\\W*$", optionsBuf.getRawBuffer());
> regEx.matches("Excel");
> }
> some details I found during debugging:
> - there is an instance of RangeToken where I have no idea where this is created. I've
set a breakpoint in the constructor but the debugger does not stop.
> - when RangeToken::getCaseInsensitiveToken is called a new RangeToken is created and
stored in fCaseIToken
> - when parsing is finished the newly created RangeToken is deleted (through ~RegularExpression
-> ~TokenFactory), but the original RangeToken (where I don't know where it is created)
still exists and references the deleted RangeToken in fCaseIToken
> - the next time RangeToken::getCaseInsensitiveToken is called the invalid reference fCaseIToken
is returned and this leads to a crash when it is accessed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1884:
-------------------------------------
Priority: Major (was: Minor)
Affects Version/s: (was: 2.7.0)
3.1.0
The problem is still present in the 3.1.0 codebase.
> Anytype prevent identity constraint application
> -----------------------------------------------
>
> Key: XERCESC-1884
> URL: https://issues.apache.org/jira/browse/XERCESC-1884
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: Linux 2.6.5-7.244-smp x86_64 GNU/Linux
> Reporter: Thomas Carcaud
> Attachments: anytype_prevent_id_constraint.xml, anytype_prevent_id_constraint.xsd
>
>
> ID declaration is not found when it is enclosed in two levels of anytype elements.
> In this example :
> <?xml version="1.0" encoding="utf-8"?>
> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
> <xs:element name="bigBadWolf">
> <xs:complexType>
> <xs:sequence maxOccurs="unbounded">
> <xs:element name="eat">
> <xs:complexType>
> <xs:attribute name="ref" type="xs:IDREF"/>
> </xs:complexType>
> </xs:element>
> </xs:sequence>
> </xs:complexType>
> </xs:element>
> <xs:element name="littlePig">
> <xs:complexType>
> <xs:attribute name="id" type="xs:ID"/>
> </xs:complexType>
> </xs:element>
> <xs:element name="world">
> <xs:complexType>
> <xs:all>
> <xs:element name="strawHouse"/>
> <xs:element name="stickHouse"/>
> <xs:element name="brickHouse"/>
> <xs:element ref="bigBadWolf"/>
> </xs:all>
> </xs:complexType>
> </xs:element>
> </xs:schema>
> <?xml version="1.0" encoding="UTF-8"?>
> <world xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="anytype_prevent_id_constraint.xsd">
> <strawHouse>
> <littlePig id="first"/>
> </strawHouse>
> <stickHouse>
> <littlePig id="second"/>
> </stickHouse>
> <brickHouse>
> <thickWall>
> <littlePig id="third"/>
> </thickWall>
> </brickHouse>
> <bigBadWolf>
> <eat ref="first"/>
> <eat ref="second"/>
> <eat ref="third"/>
> </bigBadWolf>
> </world>
> Validation fails with error "ID attribute 'third' was referenced but never declared".
Same kind of problem can be reproduced with unique/key and keyref and it also prevent duplicate
id detection.
> From my investigations in IGXMLScanner , at the brickHouse level, modelType == SchemaElementDecl::Any
will set laxThisOne to true. Then at the thickWall level, laxThisOne set fValidate to false.
And this disable the call to fICHandler->activateIdentityConstraint.
> My text editor using XercesJ 2.9.1 does not suffer from this bug.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1703:
-------------------------------------
Priority: Major (was: Minor)
Affects Version/s: (was: 2.6.0)
3.1.0
Fix Version/s: 3.1.0
Issue Type: Bug (was: Improvement)
Bug is still present in the 3.1.0 codebase. Would be nice to fix for 3.1.0.
> Bad error description reported by xerces
> ----------------------------------------
>
> Key: XERCESC-1703
> URL: https://issues.apache.org/jira/browse/XERCESC-1703
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: all platforms
> Reporter: Anton Nikolaevsky
> Fix For: 3.1.0
>
>
> xml:
> <date/>
> xsd:
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="date" type="xsd:dateTime"/>
> </xsd:schema>
> Observed: error "Datatype error: Type:SchemaDateTimeException, Message:buffer not initialized
> yet!."
> Expected error message: something like " '' is not a valid value for the type {http://www.w3.org/2001/XMLSchema}dateTime"
> An exception is thrown at XMLDateTime.hpp[411] from XMLDateTime::assertBuffer() invoked
by XMLDateTime::initParser().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1627.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
With the multiple import enabled, I get the same output with the original schema and with
the swapped include/import. There are some other schema and validation errors but I am assuming
the original bug is fixed.
> Schema validator sensitive to the order of xsd:import and xsd:include elements.
> -------------------------------------------------------------------------------
>
> Key: XERCESC-1627
> URL: https://issues.apache.org/jira/browse/XERCESC-1627
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.5.0, 2.6.0, 2.7.0
> Environment: Windows XP SR2
> Reporter: Peter Aberline
> Priority: Minor
> Fix For: 3.1.0
>
> Attachments: schema_validator_bug.zip
>
>
> Xerces validating schema parser appears to be intolerant of the order of xsd:import and
xsd:include elements.
> This can be demonstrated with the the DOMCount program:
> DOMCount -s -n -v=always CSW_caps.xml
> This causes validation errors by the schema validator unable to resolve types included
in owsGetCapabilities. Swapping the order of the
> <xsd:include> to after the <xsd:import> (lines 22-25 of CSW-discovery.xsd)
solves the validation error.
> The fragment of XMLSchema.xsd shown below suggests to me that import and include elements
can be in any order?
> http://www.w3.org/2001/XMLSchema.xsd:
> <xs:element name="schema" id="schema">
> <xs:annotation>
> <xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-schema"/>
> </xs:annotation>
> <xs:complexType>
> <xs:complexContent>
> <xs:extension base="xs:openAttrs">
> <xs:sequence>
> <xs:choice minOccurs="0" maxOccurs="unbounded">
> <xs:element ref="xs:include"/>
> <xs:element ref="xs:import"/>
> <xs:element ref="xs:redefine"/>
> <xs:element ref="xs:annotation"/>
> </xs:choice>
> <xs:sequence minOccurs="0" maxOccurs="unbounded">
> <xs:group ref="xs:schemaTop"/>
> <xs:element ref="xs:annotation" minOccurs="0" maxOccurs="unbounded"/>
> </xs:sequence>
> ...
> ...
> </xs:sequence>
> </xs:extension>
> </xs:complexContent>
> </xs:complexType>
> </xs:element>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1544:
-------------------------------------
Affects Version/s: (was: 2.7.0)
3.1.0
Still present in the 3.1.0 codebase.
> xsd:redefine recently broken
> ----------------------------
>
> Key: XERCESC-1544
> URL: https://issues.apache.org/jira/browse/XERCESC-1544
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: MacOS X, g++ build
> Reporter: Jerry Carter
> Attachments: redefine1.xsd, redefine2.xsd, redefine3.xml, redefine3.xsd
>
>
> The W3C schema for VoiceXML is quite complex and makes a good test of Xerces. Previous
versions worked well, but 2.7.0 has some problems. In addition the regexp issues (bug 1512),
xsd:redefine is also broken. This has worked in previous versions (up through 2.6.0, I believe).
> The main VXML schema <http://www.w3.org/TR/voicexml21/vxml.xsd> eventually includes
<http://www.w3.org/TR/voicexml21/vxml-synthesis-extension.xsd>. There, on line 28 is
the problem statement:
> <xsd:redefine schemaLocation="vxml-synthesis-restriction.xsd">
> This generates two classes of error messages.
> 1: Message: Could not find a declaration in the schema to be redefined corresponding
to '...'
> 2: Message: Global complexType:'...' declared more than once or also declared as simpleType
> --------------------------------------
> To reproduce, run the following lines through SAX2Print:
> <?xml version="1.0" encoding="UTF-8"?>
> <vxml version="2.1" xmlns="http://www.w3.org/2001/vxml"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://www.w3.org/2001/vxml
> http://www.w3.org/TR/voicexml21/vxml.xsd">
> <form>
> <block>
> <exit/>
> </block>
> </form>
> </vxml>
> xerces-c-src_2_7_0/bin: ./SAX2Print -v=always schema_issue.xml
> <?xml version="1.0" encoding="LATIN1"?>
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-restriction.xsd, line 30,
char 53
> Message: Could not find a declaration in the schema to be redefined corresponding to
'say-as'
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-restriction.xsd, line 43,
char 52
> Message: Could not find a declaration in the schema to be redefined corresponding to
'audio'
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-restriction.xsd, line 55,
char 38
> Message: Could not find a declaration in the schema to be redefined corresponding to
'mark'
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-extension.xsd, line 30,
char 53
> Message: Global complexType:'say-as' declared more than once or also declared as simpleType
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-extension.xsd, line 43,
char 52
> Message: Global complexType:'audio' declared more than once or also declared as simpleType
> Error at file http://www.w3.org/TR/voicexml21/vxml-synthesis-extension.xsd, line 55,
char 38
> Message: Global complexType:'mark' declared more than once or also declared as simpleType
> <vxml version="2.1" xsi:schemaLocation="http://www.w3.org/2001/vxml http://www.w3.org/TR/voicexml21/vxml.xsd">
> <form scope="dialog">
> <block>
> <exit></exit>
> </block>
> </form>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1754:
-------------------------------------
Affects Version/s: (was: 2.8.0)
3.1.0
The problem still present in the 3.1.0 codebase.
> Invalid restriction error on valid schema
> -----------------------------------------
>
> Key: XERCESC-1754
> URL: https://issues.apache.org/jira/browse/XERCESC-1754
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Environment: any
> Reporter: Boris Kolpackov
> Attachments: test.xsd
>
>
> In the attached schema, maxOccurs="1" in the sequence compositor causes Xerces-C++ to
report this schema as invalid. Changing it to "2" gets rid of the error. The same problem
exist in minOccurs="0" to minOccurs="1" restriction.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1713.
------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
The fix is in SVN. This can now be resolved by setting fgXercesLoadSchema property to false.
> external-schemaLocation property does not override the schema location attribute in the
instance
> ------------------------------------------------------------------------------------------------
>
> Key: XERCESC-1713
> URL: https://issues.apache.org/jira/browse/XERCESC-1713
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.7.0
> Environment: any
> Reporter: Boris Kolpackov
> Fix For: 3.1.0
>
>
> The documentation for the external-schemaLocation and external-noNamespaceSchemaLocation
properties state that if specified, the instance document's schemaLocation and noNamespaceSchemaLocation
attributes will be effectively ignored. This appears not to be the case. If the schema specified
with the external-* properies can not be opened, the parser proceeds to try paths from the
schemaLocation and noNamespaceSchemaLocation attributes. I think this does not make much sense
and is actually a potential security threat. Normally if one specifies the schema location
with the external-* properties they don't want the values from the instance to have any effect.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1721.
------------------------------------
Resolution: Invalid
The all compositor cannot be inside the sequence compositor. If you remove the <sequence>
tags in the referencing type, the schema becomes valid.
> Unexpected error info is reported for the group referrence(and Order indicators "all"
is used in the group definition)
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESC-1721
> URL: https://issues.apache.org/jira/browse/XERCESC-1721
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.7.0
> Environment: Windows XP
> Reporter: Bill Yan
>
> When a group is defined with Order indicators "all", and this group is refered in a complexType
definition, the schema file looks like this:
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="comment" type="xsd:string"/>
> <xsd:group name="schemaTop3">
> <xsd:all>
> <xsd:element ref="comment"/>
> </xsd:all>
> </xsd:group>
>
> <xsd:complexType name="PurchaseOrderType">
> <xsd:sequence>
> <xsd:group ref="schemaTop3" minOccurs="0" maxOccurs="0"/>
> </xsd:sequence>
> </xsd:complexType>
> </xsd:schema>
> when I use XercesDOMParser::loadGrammar() to check the validity of this schema file,
the following error info is reported:
> "A group whose content is 'all' must only appear as the content type of a complex type
definition. - Line 11, Col 61".
> I tried to change xsd:all to xsd:sequence or xsd:choice, no error is reported.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1715:
-------------------------------------
Affects Version/s: (was: 2.7.0)
3.1.0
Still present in the 3.1.0 codebase. Xerces-J 2.9.1 appears to have the same problem.
> xereces-c allows a restricted type to have mixed content, where the content type of
the base is not.
> -----------------------------------------------------------------------------------------------------
>
> Key: XERCESC-1715
> URL: https://issues.apache.org/jira/browse/XERCESC-1715
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Reporter: Christian Will
>
> Hi there,
> xereces-c allows a restricted type to have mixed content, where the content type of
the base is not.
> sample:
> <?xml version="1.0"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:complexType name="A">
> <xsd:choice minOccurs="0" maxOccurs="4">
> <xsd:group ref="x"/>
> <xsd:group ref="y"/>
> </xsd:choice>
> </xsd:complexType>
> <xsd:group name="x">
> <xsd:sequence>
> <xsd:element name="x1"/>
> <xsd:element name="x2"/>
> </xsd:sequence>
> </xsd:group>
> <xsd:group name="y">
> <xsd:choice>
> <xsd:element name="y1"/>
> <xsd:element name="y2"/>
> </xsd:choice>
> </xsd:group>
> <xsd:group name="G">
> <xsd:choice>
> <xsd:group ref="x"/>
> <xsd:group ref="y"/>
> </xsd:choice>
> </xsd:group>
> <xsd:element name="elem">
> <xsd:complexType mixed="true">
> <xsd:complexContent>
> <xsd:restriction base="A">
> <xsd:group ref="G" minOccurs="0" maxOccurs="0"/>
> </xsd:restriction>
> </xsd:complexContent>
> </xsd:complexType>
> </xsd:element>
> </xsd:schema>
> Regards,
> Christian Will
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1601.
------------------------------------
Resolution: Invalid
Does not appear to be a problem with Xerces-C++.
> SAX2 Parser throws an uncaught xercesc_2_7::XMLValid::Codes exception when setValidationConstraintFatal
is on with enclosing xml tags
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: XERCESC-1601
> URL: https://issues.apache.org/jira/browse/XERCESC-1601
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.7.0
> Environment: Xerces 2.7 recompiled locally
> Win2K, WinXP, Win2k3
> Microsoft Visual Sutudio 7.1 in either debug or release builds
> Reporter: Michel Courtine
>
> I implemented a xerces SAX2 parser by following IBM's recommandations in "Make the most
of Xerces-C++" found at:
> http://www-128.ibm.com/developerworks/xml/library/x-xercc/
> This parser works fine with large and complex files and performs a very good validation.
No complains at all.
> Untill we started to use DOM generated files by a Java app that outputs this kind of
xml data:
> <Directory xmlns="http://www.rd.bbc.co.uk/dtv/wp4/System42" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1" xsi:schemaLocation="http://www.rd.bbc.co.uk/dtv/wp4/System42 ../schema/system42.xsd">
> <ModuleEntry version="1" type="CODE" name="LIBCORE">
> </ModuleEntry>
> <ModuleEntry version="1" type="CODE" name="LIBPATH">
> </ModuleEntry>
> <ModuleEntry version="1" type="OPENTV_RESOURCE" name="SYS_ENV">
> </ModuleEntry>
> <ModuleEntry version="1" type="OPENTV_RESOURCE" name="SERVICE">
> </ModuleEntry>
> <ServiceInfo version="1" name="singleStreamVideo">
> </ServiceInfo>
> </Directory>
> When we send the following xml, with "self-contained" tags (one-liners) instead of empty-enclosing
tags, no exceptions are thrown and the validation & parsing are performed correctly.
> <Directory xmlns="http://www.rd.bbc.co.uk/dtv/wp4/System42" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
version="1" xsi:schemaLocation="http://www.rd.bbc.co.uk/dtv/wp4/System42 ../schema/system42.xsd">
> <ModuleEntry version="1" type="CODE" name="LIBCORE" />
> <ModuleEntry version="1" type="CODE" name="LIBPATH" />
> <ModuleEntry version="1" type="OPENTV_RESOURCE" name="SYS_ENV" />
> <ModuleEntry version="1" type="OPENTV_RESOURCE" name="SERVICE" />
> <ServiceInfo version="1" name="singleStreamVideo" />
> </Directory>
> An other interesting point for you is that when we turn setValidationConstraintFatal
to false or the validation off, the parsing is performed correctly too.
> This definately means to me that the validation considers the xml file as invalid although
both forms are supposed to be valid from an xsd point of view.
> (XMLSpy validates both versions against our xsd).
> On top of that, probably because because we set setValidationConstraintFatal to true,
the exception is caught internally and fails silently preventing us from catching it.
> Here is the xsd definition of a ModuleEntry:
> <xs:element name="ModuleEntry">
> <xs:annotation>
> <xs:documentation>Module entry declaration</xs:documentation>
> </xs:annotation>
> <xs:complexType>
> <xs:attribute name="name" type="xs:string" use="required"/>
> <xs:attribute name="type" use="required">
> <xs:simpleType>
> <xs:restriction base="xs:string">
> <xs:enumeration value="DIRECTORY"/>
> <xs:enumeration value="ENVIRONMENT"/>
> <xs:enumeration value="STREAMEVENTS"/>
> <xs:enumeration value="OPENTV_RESOURCE"/>
> <xs:enumeration value="SYS42_RESOURCE"/>
> <xs:enumeration value="PROPRIETARY_RESOURCE"/>
> <xs:enumeration value="CODE"/>
> <xs:enumeration value="RAW"/>
> <xs:enumeration value="VERSIONED_RAW"/>
> </xs:restriction>
> </xs:simpleType>
> </xs:attribute>
> <xs:attribute name="version" type="xs:unsignedInt" use="required"/>
> </xs:complexType>
> </xs:element>
> Here are the features we set in the compilers
> bool CParseMgr::parse(const char* sFilename, const char *sXsdPath)
> {
> CXercesInitialiser InitXerces;
> m_sFilename = sFilename;
> SAX2XMLReader* parser = XMLReaderFactory::createXMLReader();
> parser->setFeature(XMLUni::fgSAX2CoreValidation, true);
> parser->setFeature(XMLUni::fgSAX2CoreNameSpaces, true);
> parser->setFeature(XMLUni::fgXercesSchema, true);
> parser->setFeature(XMLUni::fgXercesSchemaFullChecking, true);
> parser->setValidationConstraintFatal(true);
> string schemaLocation = "http://www.rd.bbc.co.uk/dtv/wp4/System42 ";
> char *unixPath = strdup(sXsdPath);
> for (size_t i = 0; i < strlen(unixPath) - 1; i++)
> if (unixPath[i] == '\\')
> unixPath[i] = '/';
> schemaLocation += unixPath;
> free(unixPath);
> parser->setProperty(XMLUni::fgXercesSchemaExternalSchemaLocation, XMLString::transcode(schemaLocation.c_str()));
> parser->setContentHandler(this);
> parser->setErrorHandler(this);
> try
> {
> parser->parse(sFilename);
> }
> catch (const XMLException& e) {
> std::string message = m_sFilename + ":XML exception:" + XMLtoString(e.getMessage());
> Logger::StoreError( message.c_str() );
> return false;
> }
> catch (const SAXParseException& e) {
> std::string message = m_sFilename + ":SAXParse exception:" + XMLtoString(e.getMessage());
> Logger::StoreError( message.c_str() );
> return false;
> }
> catch (const SAXException& e) {
> std::string message = m_sFilename + ":SAX exception:" + XMLtoString(e.getMessage());
> Logger::StoreError( message.c_str() );
> return false;
> }
> catch (...)
> {
> string msg = m_sFilename + ":Unhandled exception in CParseMgr::parse()";
> Logger::StoreError(msg.c_str());
> return false;
> }
> delete parser;
> return true;
> }
> The exception is thrown just after the first occurence of ModuleEntry (startElement)
and before getting into the endElement Handler
> Here is a dump of the call stack a few instructions before the exception is thrown:
> > xerces-c_2_7D.dll!120a3580()
> xerces-c_2_7D.dll!120a205a()
> MSVCRTD.dll!102134ce()
> MSVCRTD.dll!102134ce()
> xerces-c_2_7D.dll!120b7324()
> xerces-c_2_7D.dll!120d545f()
> MSVCRTD.dll!10212d73()
> MSVCRTD.dll!1020b5c4()
> MSVCRTD.dll!10212a14()
> MSVCRTD.dll!102129a6()
> MSVCRTD.dll!1020e2cf()
> kernel32.dll!7c809e2a()
> xerces-c_2_7D.dll!120d54e1()
> xerces-c_2_7D.dll!12104391()
> xerces-c_2_7D.dll!12105e52()
> Tests.exe!CParseMgr::parse(const char * sFilename=0x005c0cbc, const char * sXsdPath=0x005c0ccc)
Line 43 + 0x11 C++
> Tests.exe!CScrumVTests::TestRandomFile() Line 138 C++
> Tests.exe!boost::unit_test::ut_detail::user_tc_method_invoker<CScrumVTests>::operator()()
Line 209 + 0x1c C++
> Tests.exe!boost::unit_test::ut_detail::invoker<boost::unit_test::ut_detail::unused>::invoke<boost::unit_test::ut_detail::user_tc_method_invoker<CScrumVTests>
>() Line 56 + 0x14 C++
> Tests.exe!boost::unit_test::ut_detail::callback0_impl_t<boost::unit_test::ut_detail::unused,boost::unit_test::ut_detail::user_tc_method_invoker<CScrumVTests>
>::invoke() Line 89 + 0x24 C++
> Tests.exe!boost::unit_test::callback0<boost::unit_test::ut_detail::unused>::operator()()
Line 118 + 0x26 C++
> Tests.exe!boost::unit_test::`anonymous namespace'::zero_return_wrapper::operator()()
Line 39 + 0x1a C++
> Tests.exe!boost::unit_test::ut_detail::invoker<int>::invoke<boost::unit_test::`anonymous
namespace'::zero_return_wrapper>(boost::unit_test::`anonymous-namespace'::zero_return_wrapper
& f={...}) Line 42 + 0x14 C++
> Tests.exe!boost::unit_test::ut_detail::callback0_impl_t<int,boost::unit_test::`anonymous
namespace'::zero_return_wrapper>::invoke() Line 89 + 0x20 C++
> Tests.exe!boost::unit_test::callback0<int>::operator()() Line 118 + 0x22 C++
> Tests.exe!boost::execution_monitor::catch_signals(const boost::unit_test::callback0<int>
& F={...}, bool __formal=false, bool __formal=false) Line 493 + 0x34 C++
> Tests.exe!boost::execution_monitor::execute(const boost::unit_test::callback0<int>
& F={...}, bool catch_system_errors=false, int timeout=0) Line 225 + 0x14 C++
> Tests.exe!boost::unit_test::unit_test_monitor_t::execute_and_translate(const boost::unit_test::test_case
& tc={...}) Line 56 + 0x55 C++
> Tests.exe!boost::unit_test::framework_impl::visit(const boost::unit_test::test_case
& tc={...}) Line 100 + 0xf C++
> Tests.exe!boost::unit_test::traverse_test_tree(const boost::unit_test::test_case &
tc={...}, boost::unit_test::test_tree_visitor & V={...}) Line 155 C++
> Tests.exe!boost::unit_test::traverse_test_tree(unsigned long id=65536, boost::unit_test::test_tree_visitor
& V={...}) Line 196 + 0x16 C++
> Tests.exe!boost::unit_test::traverse_test_tree(const boost::unit_test::test_suite &
suite={...}, boost::unit_test::test_tree_visitor & V={...}) Line 167 + 0xd C++
> Tests.exe!boost::unit_test::traverse_test_tree(unsigned long id=1, boost::unit_test::test_tree_visitor
& V={...}) Line 198 + 0x16 C++
> Tests.exe!boost::unit_test::framework::run(unsigned long id=1, bool continue_test=true)
Line 324 + 0xf C++
> Tests.exe!main(int argc=1, char * * argv=0x003a3768) Line 49 + 0x9 C++
> Tests.exe!mainCRTStartup() Line 259 + 0x19 C
> kernel32.dll!7c816d4f()
> ntdll.dll!7c915b4f()
> kernel32.dll!7c8399f3()
> Thanks for your time.
> Best Regards
> M
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1587.
------------------------------------
Resolution: Invalid
Works for me.
> The default values for attributes in schema are not resolved using DOMBuilder
> -----------------------------------------------------------------------------
>
> Key: XERCESC-1587
> URL: https://issues.apache.org/jira/browse/XERCESC-1587
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.6.0
> Reporter: Vit Ondruch
>
> I was used to use the XSD schema with default attribute values as:
> <xs:attribute name="MaxSequenceLength" type="xs:unsignedLong" form="unqualified" default="1"
/>
> A lot of my XML files does not contained the attributes with specified default value
at all. When i used the XercesDOMParser, everything worked as expected and when i try to retrieve
the value of such attribute, the default value was returned, but that does not apply for DOMBuilder
unfortunatelly. The attribute is simply not found, which is wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov closed XERCESC-1576.
------------------------------------
Resolution: Invalid
Please provide a test case (schema and xml files) that reproduces this problem.
> lax wildcard is handled as strict wildcard in some cases
> --------------------------------------------------------
>
> Key: XERCESC-1576
> URL: https://issues.apache.org/jira/browse/XERCESC-1576
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 2.6.0
> Environment: Windows VC++
> Reporter: Akihiko Tozawa
>
> This bug is similar to XERCESJ-128.
> When reading for example, <xs:any processContents="lax" namespace="a b c d"/>,
this "lax" is ignored and treated as "strict".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-1668:
-------------------------------------
Affects Version/s: (was: 2.7.0)
3.1.0
> Good schema rejected - simpleContent/complexContent
> ---------------------------------------------------
>
> Key: XERCESC-1668
> URL: https://issues.apache.org/jira/browse/XERCESC-1668
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Reporter: Jochen Schwarze
> Attachments: test.xml, test.xsd
>
>
> The attached schema does not validate the attached instance:
> file:///.../test.xsd:12,36: The type 'xs:anyType' specified as the base in the simpleContent
element must not have complexContent
> Both schema and instance validate in Xerces-J 2.9 (with schema-full-checking), with MSXML
4.0 and 6.0, Saxon-SA 8.8, XSV 2.10-1 and with Alphaworks' SchemaQualityChecker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779345#action_12779345
]
Boris Kolpackov commented on XERCESC-1668:
------------------------------------------
Still present in the 3.1.0 codebase.
> Good schema rejected - simpleContent/complexContent
> ---------------------------------------------------
>
> Key: XERCESC-1668
> URL: https://issues.apache.org/jira/browse/XERCESC-1668
> Project: Xerces-C++
> Issue Type: Bug
> Components: Validating Parser (XML Schema)
> Affects Versions: 3.1.0
> Reporter: Jochen Schwarze
> Attachments: test.xml, test.xsd
>
>
> The attached schema does not validate the attached instance:
> file:///.../test.xsd:12,36: The type 'xs:anyType' specified as the base in the simpleContent
element must not have complexContent
> Both schema and instance validate in Xerces-J 2.9 (with schema-full-checking), with MSXML
4.0 and 6.0, Saxon-SA 8.8, XSV 2.10-1 and with Alphaworks' SchemaQualityChecker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org
[ https://issues.apache.org/jira/browse/XERCESC-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boris Kolpackov updated XERCESC-391:
------------------------------------
Priority: Minor (was: Major)
Assignee: (was: Xerces-C Developers Mailing List)
Issue Type: New Feature (was: Bug)
> Make Error/Message Extension Of The XMLValidator Possible
> ---------------------------------------------------------
>
> Key: XERCESC-391
> URL: https://issues.apache.org/jira/browse/XERCESC-391
> Project: Xerces-C++
> Issue Type: New Feature
> Components: Validating Parser (XML Schema)
> Affects Versions: 1.7.0
> Environment: Operating System: Linux
> Platform: PC
> Reporter: Reid Spencer
> Priority: Minor
> Attachments: XMLValidator.cpp, XMLValidator.hpp, XMLValidityCodes.hpp
>
>
> The 1.7.0 xercesc/framework/XMLValidator class uses a message numbering and
> loading schema that does not lend itself to extension of the class. In my case,
> I am attempting to provide further semantic validation of a document by
> extending the class xercesc/validators/schema/SchemaValidator. To make
> XMLValidator a little more friendly to those wishing to extend it, I have
> made four new virtual functions in the XMLValidator interface. All four have
> default implementations and no code changes to any other classes were required.
> The new virtual functions are: getClassLoader, isWarning, isError, and isFatal.
> These four functions permit a subclass to determine which class loader gets
> loaded to generate the error message and to also decide which error codes are
> warnings, errors, or fatal. Previously, these capabilities were statically
> coded into XMLValidator and XMLValid. One other change is that XMLValid::Codes
> is now an unsigned integer rather than an enumeration. This change is needed
> in order to make it possible for subclasses to have their own range of error
> codes. XMLValidator reserves error numbers 0-9999 for its own use. Subclasses
> can pick any other range for their error numbers.
> The change to implement this consists of only three files:
> xercesc/framework/XMLValidator.hpp
> xercesc/framework/XMLValidator.cpp
> xercesc/framework/XMLValidityCodes.hpp
> All three files are provided as attachments and have been tested in the
> following environment (i.e. all Sample & Test programs work):
> Platform: PC (2 x 1GHz Pentium III )
> Operating System: Linux 7.1 + updates (kernel = 2.4.9-31smp)
> Compiler: GCC 3.0.3
> It would be great if these changes could be made to "stick" in future releases.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org