[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Java Technology and XML : API benchmark

• To: xml-dev <xml-dev@l...>
• Subject: Re: Java Technology and XML : API benchmark
• From: Elena Litani <elitani@c...>
• Date: Wed, 13 Mar 2002 12:47:26 -0500
• References: <575CBD83AE7DD411A23500B0D049C2F9C07751@SRVSOCRATE>

Nicolas LEHUEN wrote:
> Parsers like Xerces have dramatically grown in size
> and have performance problem due to the fact that validation is built in in
> the parser.
> To me, parsing and validating are two different activities. They may have
> been integrated for performance reasons of the parsing+validation pipeline,
> but I'd still like to have a clean, high performance parsing pipeline in
> which I could plugin any kind of validators (eg. Sun MSV).


The validation is no longer built in in the Xerces 2 parser [1]. The
parser pipeline may consist of any combinations of components. The
components, such as XML Schema Validator, can be removed or added to the
pipeline. Moreover, using XNI [2] users can write new components and add
those to the pipeline (using new parser configurations). 
For more information refer to XNI design [3].

[1] http://xml.apache.org/xerces2-j/index.html
[2] http://xml.apache.org/xerces2-j/xni.html
[3] http://xml.apache.org/xerces2-j/xni-design.html

-- 
Elena Litani / IBM Toronto

• References:
  • RE: Java Technology and XML : API benchmark
    • From: Nicolas LEHUEN <nicolas.lehuen@u...>

• Prev by Date: RE: Java Technology and XML : API benchmark
• Next by Date: RE: Java Technology and XML : API benchmark
• Previous by thread: RE: Java Technology and XML : API benchmark
• Next by thread: RE: Java Technology and XML : API benchmark
• Index(es):
  • Date
  • Thread