You are viewing a plain text version of this content. The canonical link for it is here.
Posted to announcements@xml.apache.org by Andy Clark <an...@apache.org> on 2001/08/10 13:54:55 UTC

[ANNOUNCE] Xerces 2.0.0 (beta) Release

I'm very pleased to announce the release of Xerces 2.0.0 (beta).
The Xerces2 beta release has been greatly improved since the
alpha release with an updated Xerces Native Interface (XNI) core;
the addition of the parser pipeline and configuration interfaces
to XNI; and completely re-written documentation, including lots 
of new information about XNI. The beta release is available from
the Xerces-J distribution directory:

  http://xml.apache.org/dist/xerces-j/

Xerces2 has support for XML 1.0; Namespaces; DOM 2.0 (including 
events, traversal, and range); SAX 2.0; and JAXP 1.1. Xerces2
does not yet support XML Schema and has removed support for the
deferred DOM implementation.

Xerces2 is a nearly complete rewrite of the Xerces 1.x codebase 
in order to make the code cleaner, more modular, and easier to 
maintain. Applications using only the standard interfaces such 
as JAXP, DOM, and SAX should not see any differences.

To get involved with Xerces2 development: download the beta
release, subscribe to the xerces-j-dev mailing list, and start
writing really great code!

-- 
Andy Clark * IBM, TRL - Japan * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: announcements-unsubscribe@xml.apache.org
For additional commands, email: announcements-help@xml.apache.org


Re: [ANNOUNCE] Xerces 2.0.0 (beta) Release

Posted by Andy Clark <an...@apache.org>.
Bob Jamison wrote:
> Works great! We replaced the Xerces1.4 jar in our app, and
> it worked with only minor modifications.  So it is definitely
> used in in a real-world app here.

Cool.

> The only major difference is how we access TEXT_NODEs
> within an element.  For example, if you had a tag like:
> [...]

There have been some bug fixes in the DOM implementation that
is in Xerces 1.x that have not been merged into the Xerces2
codebase. So I went ahead and synchronized the source from 
Xerces 1.x into the Xerces2 branch in CVS.

> ..as now it apparently treats TEXT_NODEs,
> ENTITY_REFERENCE_NODEs, and CDATA_SECTION_NODEs
> separately.  Once we take this into account, everything works fine.
> Is this proper operation?

Well, certainly CDATA sections and text nodes are kept as
separate nodes from each other. (This was the reason for
having the setCoalescing method on the JAXP DocumentBuilder
interface.) However, the "&quot;" entity refs appearing in
your document instance are not reported as general entity
references. So they should not be represented as entity ref
nodes in the tree.

But I checked the code and Xerces2 had a bug relating to
the entity ref nodes. We added an option that character
entity references and built-in entity refs (e.g. "&quot;")
could be communicated from the scanner. The default values
for these should have been false but, due to a bug, the
built-in entity refs were getting to the outside, ignoring
the default value of this feature. I've checked in the fix
for this bug into CVS.

If you are able to extract and build Xerces2, I'd be 
interested in knowing if your problem went away.

-- 
Andy Clark * IBM, TRL - Japan * andyc@apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org


Re: [ANNOUNCE] Xerces 2.0.0 (beta) Release

Posted by Bob Jamison <rj...@lincom-asg.com>.
Andy Clark wrote:

>I'm very pleased to announce the release of Xerces 2.0.0 (beta).
>The Xerces2 beta release has been greatly improved since the
>alpha release with an updated Xerces Native Interface (XNI) core;
>the addition of the parser pipeline and configuration interfaces
>to XNI; and completely re-written documentation, including lots 
>of new information about XNI. The beta release is available from
>the Xerces-J distribution directory:
>
>  http://xml.apache.org/dist/xerces-j/
>
>Xerces2 has support for XML 1.0; Namespaces; DOM 2.0 (including 
>events, traversal, and range); SAX 2.0; and JAXP 1.1. Xerces2
>does not yet support XML Schema and has removed support for the
>deferred DOM implementation.
>
>Xerces2 is a nearly complete rewrite of the Xerces 1.x codebase 
>in order to make the code cleaner, more modular, and easier to 
>maintain. Applications using only the standard interfaces such 
>as JAXP, DOM, and SAX should not see any differences.
>
>To get involved with Xerces2 development: download the beta
>release, subscribe to the xerces-j-dev mailing list, and start
>writing really great code!
>
Works great! We replaced the Xerces1.4 jar in our app, and
it worked with only minor modifications.  So it is definitely
used in in a real-world app here.

The only major difference is how we access TEXT_NODEs
within an element.  For example, if you had a tag like:

<sometext>&quot;<![CDATA[Hello,]]>world&quot;</sometext>

gathering up all of the TEXT_NODEs in 1.4 would result in:

"Hello, world"

in 2.0.0b, we get

world

..as now it apparently treats TEXT_NODEs,
ENTITY_REFERENCE_NODEs, and CDATA_SECTION_NODEs
separately.  Once we take this into account, everything works fine.
Is this proper operation?

Anyway, 2.0 is looking pretty good, thanks for your efforts.



Bob






---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-user-help@xml.apache.org