Shibboleth Developers

["Wilcox, Mark" <>]

Title: RE: NO FORMAL SHIB design call -- (8/8/2005)

Yeah, the xerces have to be in common/endorsed because they are essentially replacing libraries that by default come with Java (but are in the javax.* package namespace as opposed to java.* namespace, the latter cannot be replaced). The notion of "endorsed" libraries is something created by Sun to allow for this.

 

So in short - either put the JARs in common/endorsed, in jre/lib/endorsed (the univeral endorsed libray for a JVM) or upgrade to JDK 1.5 (which I believe has the libraries by default).

 

Mark W.

---

From: Jim Fox [mailto:]
Sent: Mon 8/8/2005 2:52 PM
To:
Subject: RE: NO FORMAL SHIB design call -- (8/8/2005)

>
> Unless the developers are unavailable, I'd suggest we go ahead and meet
> briefly to discuss the Java memory leak and a timeline for releasing a new
> build.
>

I tried putting the xerces jar files in "shared/lib" instead of
in "common/endorsed" - at request of some system maintainers.
That didn't work.  I got

  "Unable to parse Shibboleth Identity
   Provider configuration file: org.xml.sax.SAXParseException:
   cvc-complex-type.2.3: Element 'IdPConfig' cannot have character
   [children], because the type's content type is element-only"

on startup.  I admit to being a little out of my element
with java's and tomcat's library paths.

Jim