http://xml.apache.org/http://www.apache.org/http://www.w3.org/

Home

Readme
Installation
Build

API Docs
Samples
Programming
Migration
FAQs

Releases
Feedback

PDF Document

Download
Dev Snapshots
CVS Repository
Mail Archive

Questions
 

Answers
 
I can't use C++. Do you have a Java version?
 

Yes. The Xerces family of products also has a Java version. More information is available at: http://xml.apache.org/xerces-j/index.html


Is there any kind of support available for Xerces-C/XML4C?
 

Xerces C++ Parser somes 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 actively participate. It's up to you. Before you join these lists, you should look over the resources in the Reference Library section

Instructions for subscribing and list archives are here.

IBM also maintains a newsgroup for discussion of XML4C. The news server is "news.alphaworks.ibm.com", and the group is "XML-for-C++".


I found a defect - how do I report it?
 

Check the bug list at Apache. The problem may already be known, or even fixed.

Otherwise, send the bugs to either the xerces-c-dev mailing list (preferred) or the IBM Alphaworks news group, as desribed above. The more information that you can provide, the better the chance of understanding what happened, or what the problem really is. Please include the version of Xerces-c or XML4C, what kind of machine, including Operating System and OS Verion Number, whether you built the xerces library yourself or used the binary distribution, the XML document (or excerpt) that fails, the C++ application code that failed, and what happened.


I have a patch to the Xerces C source code. How do I submit it?
 

Mail it to the xerces-c-dev mailing list at Apache (You must be a subscriber to post to this list, but if you're considering changing the code you really want to be.) There are no set rules about how or what must be included - if you've fixed a problem or enhanced the code in some way, we really would like to get the changes back 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)




Copyright © 2000 The Apache Software Foundation. All Rights Reserved.