We've never been asked before for such a feature.  We can add it, but if
you want it immediately, just hack the source files to pass a flag through
(similar to the other Xerces options we support).

Dave



|---------+---------------------------->
|         |           michael.lessacher|
|         |           @hsbcib.com      |
|         |                            |
|         |           04/25/2002 02:56 |
|         |           AM               |
|         |                            |
|---------+---------------------------->
  
>---------------------------------------------------------------------------------------------------------------------------|
  |                                                                             
                                              |
  |        To:      [email protected]                                
                                              |
  |        cc:      (bcc: David N Bertoni/Cambridge/IBM)                        
                                              |
  |        Subject: reusing validator ala Xerces                                
                                              |
  
>---------------------------------------------------------------------------------------------------------------------------|





Xerces 1.6.0 provides a mechanism for reusing a validation grammer across a
number of XML parses. This is done via the reuseGrammar parameter of the
DOMParser::parse() method. Does Xalan 1.3 expose similar functionality
through
its public APIs?

This is useful in cases where a single parser/transformer instance is being
used
to process many XML documents, each of which is known to use the same DTD,
say.
In this case, it would be nice to avoid re-parsing the DTD on each
iteration
after the first.

As far as I understand the Xalan documentation, I can explicitly use Xerces
to
produce the DOM tree as input to XalanTransformer::transform() -- and thus
exploit Xerces' "reuseGrammar" mechanism -- but the Xalan documentation
also
claims that Xalan performs better when using its own internally constructed
DOM
tree. Thus I appear to left to choose between two sub-optimal scenarios.

Regards,
--Mike Lessacher




_____________________________________________________

This transmission has been issued by a member of the HSBC Group
"HSBC" for the information of the addressee only and should not be
reproduced and / or distributed to any other person. Each page attached
hereto must be read in conjunction with any disclaimer which forms part
of it. Unless otherwise stated, this transmission is neither an offer nor
the
solicitation of an offer to sell or purchase any investment. Its contents
are
based on information obtained from sources believed to be reliable but
HSBC makes no representation and accepts no responsibility or liability as
to its completeness or accuracy.





Reply via email to