Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] LDAPPC Problems accessing XSD files

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] LDAPPC Problems accessing XSD files

Chronological Thread 
  • From: Tom Zeller <>
  • To: Richard James <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] LDAPPC Problems accessing XSD files
  • Date: Mon, 21 May 2012 11:32:13 -0500

Thanks for pointing this out.

I have been including the xsd files in the psp distribution
(src/main/resources/schema), but sometimes forget to reference that
schema location in xml configuration files.

I don't know, is the right way to do this ? Where "this" means avoid
network dependencies ?


On Mon, May 21, 2012 at 10:21 AM, Richard James
> Hi,
> I thought I would share an issue that we encountered today with regards to
> the reference of spring-util-2.5.xsd and spring-beans-2.5.xsd in the
> Ldappc-ldap.xml file. The file points to the spring framework website at
> for some of the xsd files. As
> of around 5pm (UK time) yesterday the URL was unavailable and therefore
> stopped the LDAP provisioner from working as it was unable to access the
> xsd files.
> To get around this we have amended Ldappc-ldap.xml to point to local copies
> of these files so swapping
> xsi:schemaLocation="
> to
> xsi:schemaLocation="
> classpath:/schema/spring-beans-2.5.xsd
> classpath:/schema/spring-util-2.5.xsd"
> This fixed the problem and we are able to provision successfully. We are
> running Grouper 1.6 so it might well be that the latest config files do it
> differently.
> Typically just as we put the fix in, the spring framework website has
> become available again :) We are going to leave the files to point at local
> copies of the files to prevent this from happening again.
> Thought I best share in case anyone else has or was encountering similar
> issues.
> Cheers,
> Richie
> Regards
> Richard James
> Infrastructure Systems Administrator
> ISS Systems Architecture
> Newcastle University

Archive powered by MHonArc 2.6.16.

Top of Page