Lax validation creates conflicts over plugin content

Description

Xerces has a broken interpretation of lax validation, and allows nested instances of laxly validated elements to themselves be skipped. This masks a problem where a built-in global element in the config schema conflicts with a one-off element name used inside a plugin. Simple example is the Path element from the RequestMap conflicting with the Path element used in the File-based CredentialResolver plugin. This fails validation in most tools, but passes Xerces.

Environment

None

Activity

Scott Cantor 
December 17, 2010 at 2:39 PM

Closing after release.

Scott Cantor 
May 11, 2010 at 2:34 PM

Scott Cantor 
May 11, 2010 at 1:44 PM

Reopening to work on schema.

Scott Cantor 
November 2, 2009 at 5:12 PM

http://svn.middleware.georgetown.edu/view/cpp-sp?view=rev&revision=3178

To avoid risk for now, I'm switching to "skip" validation for ##any wildcard content, including the plugins.

##other wildcards are left as lax, since they can't conflict with content from inside this schema.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Created November 2, 2009 at 5:10 PM
Updated December 17, 2010 at 2:39 PM
Resolved May 11, 2010 at 2:34 PM