shibboleth-dev - RE: [Shib-Dev] [Patch] SP Config schema bug for <Path>
Subject: Shibboleth Developers
List archive
- From: "Scott Cantor" <>
- To: <>
- Subject: RE: [Shib-Dev] [Patch] SP Config schema bug for <Path>
- Date: Fri, 23 Oct 2009 12:16:01 -0400
- Organization: The Ohio State University
Any chance you're using a separate tool to validate the file and it's what's
reporting the violation?
The Xerces validator doesn't notice this because it's laxly validating the
wildcard content of CredentialResolver and thus skipping it. That's
technically correct behavior, and is one of the reasons I don't require
schemas and validation on the content models of the plugins. That's all
handled manually.
So on one level your tool (if I'm guessing correctly) may have a bug, and I
would note that the concern about what's "legal" inside the plugins is
really beside the point because anything is legal there. It's an open
content model with a wildcard. You can stick anything in, it just won't load
the plugin (and it will tell you that).
The schema's not as consistent as I would like in that it does define a
number of local elements, so I'm inclined to consider revising it, but I
have to be very careful not to invalidate any existing instances, so it has
to be done very deliberately.
Renaming an element (without removing the original) is a way of avoiding
that testing because I can guarantee nothing new will break and the old
stuff that worked already keeps working.
-- Scott
- [Patch] SP Config schema bug for <Path>, Daniel F Crisman, 10/23/2009
- RE: [Shib-Dev] [Patch] SP Config schema bug for <Path>, Scott Cantor, 10/23/2009
- RE: [Shib-Dev] [Patch] SP Config schema bug for <Path>, Scott Cantor, 10/23/2009
Archive powered by MHonArc 2.6.16.