RE: Tomcat 7.0.50 tldValidation

2014-02-25 Thread Paul Beckett
Konstantin,Thanks this has fixed it for me. > > I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50. > > After upgrading I got lots of the below errors recorded in catalina.out > > The errors are not logged if I disable tldValidation (either by settings > > tldValidation=false in cont

Re: Tomcat 7.0.50 tldValidation

2014-02-25 Thread Konstantin Kolinko
2014-01-22 18:12 GMT+04:00 Paul Beckett : > I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50. > After upgrading I got lots of the below errors recorded in catalina.out > The errors are not logged if I disable tldValidation (either by settings > tldValidation=false in context.xml or

RE: Tomcat 7.0.50 tldValidation

2014-02-25 Thread Paul Beckett
> Date: Wed, 22 Jan 2014 15:15:53 + > From: ma...@apache.org > To: users@tomcat.apache.org > Subject: Re: Tomcat 7.0.50 tldValidation > > On 22/01/2014 14:12, Paul Beckett wrote: > > Does anyone know: > - Why this occurs only since 7.0.50 > Changes to XML v

Re: Tomcat 7.0.50 tldValidation

2014-01-28 Thread Mark Thomas
On 28/01/2014 15:15, Christopher Schultz wrote: > There is no reason, however, that we couldn't merge the schemas > together into a single file Yes there is. Licensing. > I've gotten lost in the various resolver classes. Which one were > you looking at? There is only one EntityResolver / Entit

Re: Tomcat 7.0.50 tldValidation

2014-01-28 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/24/14, 3:53 AM, Mark Thomas wrote: > On 23/01/2014 15:25, Christopher Schultz wrote: >> On 1/23/14, 10:17 AM, Mark Thomas wrote: >>> On 23/01/2014 15:11, Christopher Schultz wrote: > If that's true, then the Digester should be using

Re: Tomcat 7.0.50 tldValidation

2014-01-26 Thread Konstantin Kolinko
2014-01-24 Konstantin Kolinko : > 2014/1/24 Mark Thomas : >> On 23/01/2014 15:25, Christopher Schultz wrote: >>> On 1/23/14, 10:17 AM, Mark Thomas wrote: On 23/01/2014 15:11, Christopher Schultz wrote: >> > If that's true, then the Digester should be using the public > namespace id of

Re: Tomcat 7.0.50 tldValidation

2014-01-24 Thread Konstantin Kolinko
2014/1/24 Mark Thomas : > On 23/01/2014 15:25, Christopher Schultz wrote: >> On 1/23/14, 10:17 AM, Mark Thomas wrote: >>> On 23/01/2014 15:11, Christopher Schultz wrote: > If that's true, then the Digester should be using the public namespace id of the schema and ignoring the (incomplete)

Re: Tomcat 7.0.50 tldValidation

2014-01-24 Thread Mark Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/2014 15:25, Christopher Schultz wrote: > On 1/23/14, 10:17 AM, Mark Thomas wrote: >> On 23/01/2014 15:11, Christopher Schultz wrote: >>> If that's true, then the Digester should be using the public >>> namespace id of the schema and ignoring

Re: Tomcat 7.0.50 tldValidation

2014-01-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/23/14, 10:17 AM, Mark Thomas wrote: > On 23/01/2014 15:11, Christopher Schultz wrote: >> Mark, > >> On 1/23/14, 7:54 AM, Mark Thomas wrote: >>> On 23/01/2014 12:20, Paul Beckett wrote: > As this wasn't a problem in 7.0.47, do you

Re: Tomcat 7.0.50 tldValidation

2014-01-23 Thread Mark Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/2014 15:11, Christopher Schultz wrote: > Mark, > > On 1/23/14, 7:54 AM, Mark Thomas wrote: >> On 23/01/2014 12:20, Paul Beckett wrote: > >>> As this wasn't a problem in 7.0.47, do you know what's >>> changed, and if this is something I can

Re: Tomcat 7.0.50 tldValidation

2014-01-23 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/23/14, 7:54 AM, Mark Thomas wrote: > On 23/01/2014 12:20, Paul Beckett wrote: > >> As this wasn't a problem in 7.0.47, do you know what's changed, >> and if this is something I can configure at the Tomcat level >> without too much pain?

Re: Tomcat 7.0.50 tldValidation

2014-01-23 Thread Mark Thomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/01/2014 12:20, Paul Beckett wrote: > As this wasn't a problem in 7.0.47, do you know what's changed, and > if this is something I can configure at the Tomcat level without > too much pain? See my previous response. > Also you mentioned the po

RE: Tomcat 7.0.50 tldValidation

2014-01-23 Thread Paul Beckett
my ignorance in this area). Thanks again,Paul > Date: Wed, 22 Jan 2014 10:24:20 -0500 > From: ch...@christopherschultz.net > To: users@tomcat.apache.org > Subject: Re: Tomcat 7.0.50 tldValidation > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Mark, > > On

Re: Tomcat 7.0.50 tldValidation

2014-01-22 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Mark, On 1/22/14, 10:15 AM, Mark Thomas wrote: > On 22/01/2014 14:12, Paul Beckett wrote: >> Does anyone know: > - Why this occurs only since 7.0.50 Changes to XML validation > introduced in 7.0.48->7.0.50 > > - Where the root issue is likely to be

Re: Tomcat 7.0.50 tldValidation

2014-01-22 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Paul, On 1/22/14, 10:20 AM, Christopher Schultz wrote: > Paul, > > On 1/22/14, 9:12 AM, Paul Beckett wrote: >> I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50. >> After upgrading I got lots of the below errors recorded in >> cata

Re: Tomcat 7.0.50 tldValidation

2014-01-22 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Paul, On 1/22/14, 9:12 AM, Paul Beckett wrote: > I've recently upgraded some of our tomcats from 7.0.47 to 7.0.50. > After upgrading I got lots of the below errors recorded in > catalina.out The errors are not logged if I disable tldValidation > (e

Re: Tomcat 7.0.50 tldValidation

2014-01-22 Thread Mark Thomas
On 22/01/2014 14:12, Paul Beckett wrote: > Does anyone know: - Why this occurs only since 7.0.50 Changes to XML validation introduced in 7.0.48->7.0.50 - Where the root issue is likely to be / how to fix it Psi probe ships with an implementation of the standard tag library that includes the follow