Great stuff, we only exist for a week and already the first improvements
to doc's and code are coming in.

You (and all other's) can help even more by doing the 
following:

        # make a copy of the whole trhee
        cp -r xerces xerces.orig
        # make your changes
        cd xerces/....
        vi ...
        # make a diff
        diff -c3 -r xerces.orig xerces > patch
        # and email the patch :-) together with why and
        # what you changed :-)

Or if you have used anonymous CVS

        # make sure you have the last version
        cvs update
        # make your changes
        cd xerces/...
        vi ....
        # and make a diff
        cvs diff > patch
        # and email the patch :-) with a small description
        # of what and why. Preferably NOT as an attachement.

And that is it. Regardless of wether you are hacking code or doc's, this
is _the_ way to make sure it ends up in the next release. If you do _NOT_
want to be mentioned in the contributor's/STATUS file, make sure you say
so. In that case you are kept anonymous. 

There is a punishment if you send patches too often.... as you then end up
with direct commit access :-) 

DW

On Thu, 11 Nov 1999, Shaoping Zhou wrote:

> Hi all,
> 
> Just joined this evening, and downloaded xercesJ. While going through FAQ to 
> learn about xercesJ by writing some sample code, I found this typo under:
> 
> http://xml.apache.org/xerces-j/faq-write.html#3
> 
> The second way to instantiate a parser class is to explicitly instantiate the 
> parser class, as shown in this example, which is creating a DOM Parser. Use 
> this way when you know exactly which parser configuration you need, and you 
> are sure that you will not need to switch configurations.
> 
>      
>                 
> import org.apache.xerces.parsers.DOMParser;
> import org.w3c.com.Document;
> import org.xml.sax.SAXException;
> import java.io.IOException;
> 
>      
> 
> org.w3c.com.Document shall be changed to org.w3c.dom.Document
> 
> By the way, I was able to compile everything including the sample code under 
> JBuilder 3. The 2 UI based examples looks really good, but I guess I need a 
> week or so to really appreciate what is behind those screens. 
> 
> Thanks for all the good work so far.
> 
> best regards,
> -Shaoping Zhou
> 

Reply via email to