'>

'>

'>

'>

'>

'>

'>

Please report bugs to Jira, the Apache bug database. Pick the product "Xerces-C++" using the following components&colon;

Component | Description
--- | ---
DOM | Items specific to DOM
SAX/SAX2 | Items specific to SAX or SAX2
Non-Validating Parser | General Parsing Problem
Validating Parser (DTD) | DTD related parser issue
Validating Parser (Schema) | Schema related parser issue
Utilities | Items related to utilities like MessageLoader, Transcoder, NetAccessors, Platform specific utilities
Build | Problem with build, makefile, project files
Documentation | Documentation bugs such as FAQ, Programming Guide
Samples/Tests | Samples or test cases related issues
Miscellaneous | Items not covered in other categories

A copy of your bug report is sent automatically to the discussion list &XercesCName; development mailing list.

Search first

Check the Jira database before submitting your bug report to avoid creating a duplicate report. Even the bug has been reported already, you may add a comment to the existing report since your contribution may lead to a quicker identification/resolution to the bug reported.

Here is the list of outstanding bugs that are currently reported in Jira.

Write a good bug report

Writing a useful bug report, which makes the bug reproducible, is the first step towards the resolution of the bug. Specifics about the bug, like

- &XercesCName; version number
- Platform
- Operating system and version number
- Compiler and version number
- The XML document (or excerpt) that failed
- The C++ application code that failed
- Whether you built the &XercesCName; library yourself or used the binary distribution
- What happened

are all necessary information to allow developer to reproduce, identify, evaluate and eventually, fix the bug, which is the very purpose of your reporting of the bug.

If you are providing a patch please review the information in Submitting Patches.

'>

Operating System
Compiler
32-bit binary
Windows 2000
MS Visual C++ 6.0 SP3
AIX 5.1
xlC_r 6.0.0
Solaris 2.8
Forte C++ Version 6 Update 2
HP-UX 11i
aCC A.03.52 with pthreads
RHEL 4.0 (IA32)
gcc 3.4.3
64-bit binary
AIX 5.1
xlC_r 6.0.0
Solaris 2.8
Forte C++ Version 6 Update 2
HP-UX 11i
aCC A.03.52 with pthreads
SuSE Linux 8.0 (AMD64)
gcc 3.2.2
'>

If you are not using any of these compilers, you are taking a calculated risk by exploring new grounds. Your effort in making &XercesCName; work on this new compiler is greatly appreciated and any problems you face can be addressed on the &XercesCName; user mailing list. '>

Is there any kind of support available for &XercesCName;?

&XercesCName; comes with no formal support.

Every volunteer project obtains its strength from the people involved in it. Mailing lists provide a simple and effective communication mechanism. You are welcome to join any of these mailing lists (or all of them if you wish). You can choose to lurk, or to actively participate. It is up to you. Before you join these lists, you should look over the resources in the Reference Library section

Instructions for subscribing are at http&colon;//xml.apache.org/mail.html. Archives of the lists are available from http&colon;//marc.theaimsgroup.com/?l=xerces-c-dev

'>

I have a patch to the &XercesCName; source code. How do I submit it?

Mail it to the &XercesCName; development mailing list. Its also a good idea to add a report to Jira to track the issue There are no set rules about how or what must be included -- if you have fixed a problem or enhanced the code in some way, we really would like to get your changes, and will take them in any reasonable form.

Generally a diff of the changed files against the current sources from CVS is good, along with some kind of description of what the change is. (Working with the current sources is important!)

'>

FAQ&colon; What platforms / compilers are being used to build the binary distribution kits?) '>

FAQ&colon; Which DLLs do I need to distribute with my application?) '>

FAQ for more information. '>

For future release plan about &XercesCName;, please refer to Releases Plan.

'>

We would very much appreciate feedback on the package via the &XercesCName; mailing list &XercesCUserEmailAddress; , and we encourage the submission of bugs as described on our Bug-Reporting page. Please read this document before using this package. '>

Please browse through this bundled documentation completely. Most of the common questions have been answered in the FAQs. Specifically, do read the answer to " Is there any kind of support available for &XercesCName;?". Browsing this documentation, may be the quickest way to get an answer. Of course, if all else fails, as mentioned in the link above, you can post a question to the &XercesCName; user mailing list.

See Bug Reporting if you would like to report a defect (greatly appreciated!).

'>