Yes, that would likely be the problem.  I'll take a look and see what the
issues are.  I'm particularly concerned with the memory leaks, so we'll
have to be careful to make sure we don't do this until any real memory
leaks are fixed.

Dave



                                                                                       
           
                    Paul Emberson                                                      
           
                    <[EMAIL PROTECTED]        To:     [EMAIL PROTECTED]              
           
                    uk>                  cc:     (bcc: David N Bertoni/CAM/Lotus)      
           
                                         Subject:     Re: Validation problems with 
XalanC v1.2    
                    08/23/2001                                                         
           
                    10:07 AM                                                           
           
                    Please                                                             
           
                    respond to                                                         
           
                    xalan-dev                                                          
           
                                                                                       
           
                                                                                       
           



I may have found the source of the problem.

In XalanSourceTree\XalanSourceTreeParserLiaison.cpp

there are two instances of parseXMLStream()

This one,

void
XalanSourceTreeParserLiaison::parseXMLStream(
                         const InputSource&              theInputSource,
                         ContentHandler&                 theContentHandler,
                         DTDHandler*
theDTDHandler,
                         LexicalHandler*                 theLexicalHandler,
                         const XalanDOMString&   /* theIdentifier */)

contains the line

         theReader->setFeature(
                 validationString,
                 m_xercesParserLiaison.getUseValidation());


however

XalanDocument*
XalanSourceTreeParserLiaison::parseXMLStream(
                         const InputSource&              inputSource,
                         const XalanDOMString&   /* identifier */)



doesn't.

I added it and validation worked ok using testXSLT but it reported a load
of memory leaks.

I don't know if this is the problem but I'll add it to the bug report.


Another question, Is it possible to set validation using the
XalanTransformer class?  I don't see that it is but it would be useful.

Paul



At 10:51 22/08/01 -0400, you wrote:

>I don't think this has anything to do with Win98 -- it's probably
something
>related to changes in Xerces.  It shouldn't have anything to do with the
>stylesheet and you can now use the VALIDATE option even if you're
>stylesheet doesn't have a DTD, because we no longer turn on validation for
>stylesheet processing.
>
>Can you reduce the problem to a minimal set of documents and enter a bug
>into bugzilla?
>
>Dave
>
>
>
>
>
>                       Paul
> Emberson
>
>                       <[EMAIL PROTECTED]>         To:
> [EMAIL PROTECTED]
>                                                cc:      (bcc: David N
> Bertoni/CAM/Lotus)
>                       08/22/2001 06:22         Subject: Validation
> problems with XalanC v1.2
>                       AM
>
>                       Please
> respond
>
>                       to
> xalan-dev
>
>
>
>
>
>
>
>
>Dear all,
>
>I have a stylesheet which relies on default attributes specified in the
>dtd, specified in the DOCTYPE of an input xml document.  Using testXSLT
>with v1.1 this worked.  Now it doesn't.  (It only looks at attributes
>explicitly written in the input document.)
>
>I have tried using the -VALIDATE argument.  However my XSL document
doesn't
>
>have a DTD.  Is this the reason?  Is there anyway to only validate the xml
>document? (From command line or through the API.)  There seems to be no
>difference when using the -VALIDATE option.  There are never any errors
>thrown up even when the XML document is invalid (but still well formed).
>
>Validation using xerces samples works.  (e.g sax2count -v=always will
throw
>
>up errors if the xml is invalid.)
>
>I'm using Win98 which Xalan doesn't explicitly support.  Could it be
>causing a problem here?
>
>Many thanks,
>
>Paul Emberson





Reply via email to