Shibboleth Developers

[Jan Peter Stotz <>]

Hi Chad,

I am aware that my understanding of some involved topics is not complete
but IMHO it is not the XML Schema - it is more the SpringFramework
Schema loading and extension as it it uses in Shibboleth with one base
schema and and the extended schema in a different file. That is all far
away from any any standard XML Schema usage.

BTW: I have imported my custom name space in handlers.xml including the
xsi:schemaLocation definition. But as I said there no example available
to show how to use my custom name space.

In handlers.xml only ProfileHandler and LoginHandler elements are
allowed therefore my name space can not be used on that level. the
xsi:type is also fixed. Replacing the standard name space with my custom
name space doesn't work either - then I get the mentioned problem with
<import> element and the targetNamespace attributes mentioned in my OP.

Ciao Jan

Chad La Joie wrote:
> At the XML level there is no difference between "extending" an existing
> type and creating a new type.  The config doesn't care if, under the
> hood, you've extended a class it already knows about.
> 
> What you're missing is a basic understanding of XML Schema[1], which, as
> the documentation said, is a requirement for creating these new plugins.
>  In particular you haven't declared your namespace within the
> handler.xml and used the associated prefix with the type.
> 
> [1] http://www.w3schools.com/schema/default.asp