How to avoid startup XML parser errors

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

How to avoid startup XML parser errors

Jeroen Hoffman
Hi,

A known issue is that on startup, a couple of errors are logged regarding XML
parsers, like:
"Checking for Xerces, found version Xerces-J 2.9.0 needed version Xerces-J 2.9.1
Warning: Failed find a valid Parser!"

In http://www.nabble.com/Deploying-to-Tomcat-6.0-td22033371.html, Alex already
said: "no worries: this is just eXist telling you it doesn't find the version of
Xerces and Xalan it expects, but this isn't a problem."

All functions well indeed, however, ignoring errors can be considered bad
practice by professional deployment parties. Therefore, if I was to remove the
error logging, how would I go about? Is it a question of moving well-versioned
jars around or is there more to it?


Thanks in advance
Jeroen Hoffman












--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: How to avoid startup XML parser errors

Erik Bruchez
Administrator
Jeroen,

We include eXist 1.2.6 (with some patches) in recent nightly builds  
and these warnings are removed in recent builds.

So you can either use the latest code, or in the Orbeon CVS, check  
orbeon/tools/eXist-1_2_6-20090702.patch to see the diffs from stock  
eXist 1.2.6.

-Erik

On Jul 8, 2009, at 7:27 AM, Jeroen Hoffman wrote:

> Hi,
>
> A known issue is that on startup, a couple of errors are logged  
> regarding XML parsers, like:
> "Checking for Xerces, found version Xerces-J 2.9.0 needed version  
> Xerces-J 2.9.1
> Warning: Failed find a valid Parser!"
>
> In http://www.nabble.com/Deploying-to-Tomcat-6.0-td22033371.html,  
> Alex already said: "no worries: this is just eXist telling you it  
> doesn't find the version of Xerces and Xalan it expects, but this  
> isn't a problem."
>
> All functions well indeed, however, ignoring errors can be  
> considered bad practice by professional deployment parties.  
> Therefore, if I was to remove the error logging, how would I go  
> about? Is it a question of moving well-versioned jars around or is  
> there more to it?
>
>
> Thanks in advance
> Jeroen Hoffman
>
>
>
>
>
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the [hidden email]  
> mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: How to avoid startup XML parser errors

Jeroen Hoffman

A recent build will do nicely, thanks for the info!

Jeroen


Erik Bruchez wrote:

> Jeroen,
>
> We include eXist 1.2.6 (with some patches) in recent nightly builds and
> these warnings are removed in recent builds.
>
> So you can either use the latest code, or in the Orbeon CVS, check
> orbeon/tools/eXist-1_2_6-20090702.patch to see the diffs from stock
> eXist 1.2.6.
>
> -Erik
>
> On Jul 8, 2009, at 7:27 AM, Jeroen Hoffman wrote:
>
>> Hi,
>>
>> A known issue is that on startup, a couple of errors are logged
>> regarding XML parsers, like:
>> "Checking for Xerces, found version Xerces-J 2.9.0 needed version
>> Xerces-J 2.9.1
>> Warning: Failed find a valid Parser!"
>>
>> In http://www.nabble.com/Deploying-to-Tomcat-6.0-td22033371.html, Alex
>> already said: "no worries: this is just eXist telling you it doesn't
>> find the version of Xerces and Xalan it expects, but this isn't a
>> problem."
>>
>> All functions well indeed, however, ignoring errors can be considered
>> bad practice by professional deployment parties. Therefore, if I was
>> to remove the error logging, how would I go about? Is it a question of
>> moving well-versioned jars around or is there more to it?
>>
>>
>> Thanks in advance
>> Jeroen Hoffman
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> You receive this message as a subscriber of the [hidden email]
>> mailing list.
>> To unsubscribe: mailto:[hidden email]
>> For general help: mailto:[hidden email]?subject=help
>> OW2 mailing lists service home page: http://www.ow2.org/wws
>
> --
> Orbeon Forms - Web Forms for the Enterprise Done the Right Way
> http://www.orbeon.com/
>


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws