Mark / Chris,Thanks for your responses, and telling me how I can fix this for a particular application. That's greatly appreciated. I maintain several tomcat servers, and have encountered this issue on all three of the applications were I've upgraded Tomcat. This hadn't been an issue for me with earlier Tomcat releases: 7.0.47 and earlier. Ideally I would like to fix this at a tomcat level, rather than modifying several different (sometimes third-party proprietary) applications. 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? Also you mentioned the possibility of "include the spec-appropriate TLD Schema along with Tomcat", is this something I could configure easily? If so, would you be able to point me in the right direction (apologies for 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 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 / how to fix it Psi probe > > ships with an implementation of the standard tag library that > > includes the following: > > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > > web-jsptaglibrary_2_0.xsd" > > > > in a tag library descriptor. The "web-jsptaglibrary_2_0.xsd" is a > > hint to the location but that is not enough for Tomcat to identify > > it. Later versions of the standard tag library use: > > > > xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee > > http://java.sun.com/xml/ns/j2ee/web-jsptaglibrary_2_0.xsd"; > > > > which is unique so Tomcat is able to identify it. > > > > One could argue that web-jsptaglibrary_2_0.xsd should be sufficient > > to identify location of the intended schema. > > Would it be worth it to include the spec-appropriate TLD Schema along > with Tomcat so that simply mentioning the system id would be enough > for Tomcat to recognize it when configuring the digester? > > - -chris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQIcBAEBCAAGBQJS3+KkAAoJEBzwKT+lPKRYZjQQAJzIJIP9nQXs6CfKFoN8Y+Ay > xDfCyiUgreAPvtCdGj6PbtsOQoei1sr+c52Dgyz7YYuMZjZhCYCF38BFhsNyhHrw > SWRRs8MIqbYnR7NU2YX22HEcf84SCBXMNK7+K261zlGAFsuYCTFoeOaCx3z/f993 > jiPbZfjY0cNHNKJS3VilItUzjdH73noWhjmAHUVQJ4gD5Aa+ZI2f5Enbw0lGXIm1 > RSOLJ7+9Zm6AKqeJ+pI4mARxUK9crXqMbmaT/RZKj9zV3T0GrMcUvc7BtvGHsKTv > JBckJKleb1dx1hCM1r9XqMvaQ8gU623NYDPq+9w6+cJQdR6oEtBCL3ayLfVTX5Dz > PQqmvn8WZUxi7xuENvzlqljfmF6xoFKCfRTHmuiyusch77KsmVHMNJDkoEUhccrE > G6Qy749nIIvvhaBMAzSD174XijSiBSAuJxn+zZyiojAcd9S37f4ZKn8cCnTPPZdp > XRV3F/tD802qFfKHr887OxIchpKsyTlXSnWVuXYEasg09kPAYNCa6tCZ5xHRazr+ > suwM301luStIs3EF+goix5H0njFaQO9bWvVNnjJyvKlQfxJqVyQseMCjDBwYa05C > n55LJi0H0Jl3i7qmpLvVIzX54HsUsJiKYp6JCOlNYoVXaZm7xlVtWoZwXj370yX/ > Bh3LLh2/gUMPEIn9QeaU > =eXbe > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org >
