Skip to Content.
Sympa Menu

mace-opensaml-users - Re: Open SAML 2 Libaries

Subject: OpenSAML user discussion

List archive

Re: Open SAML 2 Libaries


Chronological Thread 
  • From: Arnout Engelen <>
  • To: Peter Gambino <>
  • Cc:
  • Subject: Re: Open SAML 2 Libaries
  • Date: Tue, 08 Jan 2008 22:55:11 +0100

On Tue, Jan 08, 2008 at 03:56:07PM -0500, Peter Gambino wrote:
> 2008-01-08 15:41:53,809 ERROR [STDERR] ERROR: 'UndeclaredPrefix: Cannot
> resolve 'xt:DEFAULT' as a QName: the prefix 'xt' is not declared.'
> 2008-01-08 15:41:53,809 ERROR [org.opensaml.xml.XMLConfigurator]
> Configuration file does not validate against schema
> org.xml.sax.SAXParseException: UndeclaredPrefix: Cannot resolve 'xt:DEFAULT'
> as a QName: the prefix 'xt' is not declared.
> at
> com.sun.org.apache.xerces.internal.jaxp.validation.Util.toSAXParseException(
> Util.java:109)
> at
> com.sun.org.apache.xerces.internal.jaxp.validation.ErrorHandlerAdaptor.error
> (ErrorHandlerAdaptor.java:104)

FWIW: I've also seen this error at some point, I believe when unittesting my
code, *after* adding a parameter to the jvm to endorse xalan/xerces.

I ended up just disabling the SAML component (as it wasn't neccessary for this
particular set of scripts anyway), so this won't help you much. The same
component works fine in production (running in a servlet container which
endorses xalan/xerces), however, so I'm pretty sure the validity of the XML
isn't the root of the problem.

I'd also be interested in finding out what the cause of and the solution for
this problem is.


Arnout



Archive powered by MHonArc 2.6.16.

Top of Page