Shibboleth Developers

[Jan Peter Stotz <>]

Hi Jeff,

you were right, there was a small mistake. In my case in the SCHEMA_TYPE
definition in the BeanDefinitionParser. After correcting that I got some
new error messages about a non-writable authenticationMethod attribute
field. I fixed that by implementing the Bean Factory (I used the direct
method presented on the main IdPDevCustomExtension page). And finally it
worked.

Thanks to everybody who helped especially Chad for his patience.

BTW: The presented steps for installing the custom extension are IMHO
way too complicated as they had to be. I prefer a much quicker variant:

Using Tomcat it doesn't matter if the idp.war is packed as a zip or
unpacked as a directory. Using it unpacked as "idp" directory in the
webapps directory allows direct adding/updating of libraries and editing
the web.xml file.
Then you only have to restart tomcat (because of a bug in logback which
prevents directly updating the idp webapp while tomcat is running) after
copying an updated library into the WEB-INF/lib directory. In
combination of starting tomcat from withing Eclipse via server
configuration debugging is finally as comfortable as I expect it...

Ciao Jan

Jeff.Krug wrote:
> I am coming into this rather late and without certainty on everything
> you have tried, but I know that when I developed my first couple of
> custom data connectors, I had a few issues with the Bean Definition
> stuff, because I didn't realize how tightly the XML to Java bindings
> were.  I think I have seen that error before, and for me it was
> because I had an inconsistency in my Java code and XSD in terms of
> the name of a type.  I would recommend just doing a once over and
> make sure you didn't typo anything in the XML config file, the XSD,
> or the Java code.