Grouper Users - Open Discussion List

[Tom Zeller <>]

Building is probably less of a concern, if at all, than runtime.

> Right, this is definitely a concern.  I think we went through this before 
> and moved a lot of external xsds to internal (not sure which version of 
> Grouper), but maybe not all of them.  I opened a jira:
>
> https://bugs.internet2.edu/jira/browse/GRP-796
>
> I wonder if the pom.xmls can (or need to) be refactored as well...
>
> <project xmlns="http://maven.apache.org/POM/4.0.0"; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/maven-v4_0_0.xsd";>
>
> Thanks,
> Chris
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Nathan Kopp
> Sent: Monday, May 21, 2012 11:52 AM
> To: Richard James; 
> 
> Subject: [grouper-users] RE: LDAPPC Problems accessing XSD files
>
> I'm personally of the opinion that referencing external schemas in an 
> operational XML document is a bad idea... for this exact reason.  I don't 
> like depending on an external resource that is out of control, especially 
> when it's not a necessity and there isn't any other functional dependency 
> on that external resource.  I think it's much safer to package a local copy.
>
> -Nathan
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Richard James
> Sent: Monday, May 21, 2012 11:21 AM
> To: 
> 
> Subject: [grouper-users] LDAPPC Problems accessing XSD files
>
> 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 
> http://www.springframework.org/schema/util/ 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="http://www.springframework.org/schema/beans 
> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>    http://www.springframework.org/schema/util 
> http://www.springframework.org/schema/util/spring-util-2.5.xsd";
>
> to
>
> xsi:schemaLocation="http://www.springframework.org/schema/beans 
> classpath:/schema/spring-beans-2.5.xsd
>      http://www.springframework.org/schema/util 
> 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
>
>