David Bertoni wrote:
>[EMAIL PROTECTED] wrote:
>>> -----Original Message-----
>>> From: David Bertoni [mailto:[EMAIL PROTECTED]
>>> Sent: Thursday, February 07, 2008 4:31 PM
>>> To: [email protected]
>>> Subject: Re: Xerces 2.8 on HP-UX with GCC - EndOfEntityException
>>>
>>> [EMAIL PROTECTED] wrote:
>>>> I have successfully built and used Xerces on Linux, Solaris and OSX
>>> and
>>>> used it to validate documents but when I try the same on HP-UX
>11.11,
>>> I
>>>> get EndOfEntityExceptions when calling the parser's loadGrammar
>> method
>>>> to load xml.xsd
>>> That's normal processing, and the exception should be caught inside
>the
>>
>> The first part is normal but, as you say, the exception should be
>caught
>> by the library but is not caught on HPUX..
>Then something in your toolchain is broken.

Why would this break for only one platform? I have gcc and g++ on all my
platforms and use the native linker on each.  I have the same Makefiles
for the codebase regardless of the platform.

>
>>
>>> library.  Can you be more specific about what you mean by "I get
>>> EndOfEntityExceptions?"  Can you run the sample command line
>>> applications?
>>
>> Yes, I can run the command line applications without problems,
>> particularly SCMPrint which is the only sample that uses loadGrammar.
>Then something broken in the way you're building your code.  Are you
>linking using gcc instead of g++?  That could be one reason why your
>application doesn't work properly.


I will check on this but as I don't follow why it would break on only of
four platforms.

>
>>
>> The API documentation indicates that loadGrammar can throw one of
>> SAXException, DOMException or XMLException. Would it be safe to
ignore
>> EndOfEntityException if it is not indicating an error?
>If that exception leaks out of loadGrammar, then something is very
>broken,
>so it doesn't matter if you ignore it or not.

Good to know. 
Thanks for the suggestions.

//M

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to