Skip to Content.
Sympa Menu

grouper-dev - RE: [grouper-dev] ldappc <include file=ldappc-other.xml /> ?

Subject: Grouper Developers Forum

List archive

RE: [grouper-dev] ldappc <include file=ldappc-other.xml /> ?

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Tom Zeller <>, Grouper Dev <>
  • Subject: RE: [grouper-dev] ldappc <include file=ldappc-other.xml /> ?
  • Date: Fri, 23 Jan 2009 13:54:57 -0500
  • Accept-language: en-US
  • Acceptlanguage: en-US

Are we talking about 1.4.1 or 1.5?


If 1.5…


I would like to solve this problem for grouper and subject config files too.  We did have ideas (or maybe just me), about being able to manage various environments of grouper and keep only the differences in various diff files (e.g. if there are two differences in for prod, maybe there is a with two settings, and grouper will overlay those on top of the base  We do this at Penn for our framework XML config file and it works nicely.  Then we build all envs at once, and end up with a bunch of warfiles or whatever the output is, one for test, prod, etc.  I think the new web frameworks do similar things (e.g. rails).  This would be a little more complicated for grouper since we have so many config files, and we have properties files vs xml files.  I wonder if we should consolidate some of our config files or decide if we want to standardize on properties files vs xml…


OK, let me answer your question, Im hesitant to do a non vanilla XML feature since it might make things harder later… (e.g. for prompting to see if right server, I just parse the XML file, maybe that would stop working).  But we could have a param in there that says which XML to look at, so it is like a manual include…





From: [mailto:] On Behalf Of Tom Zeller
Sent: Friday, January 23, 2009 11:47 AM
To: Grouper Dev
Subject: [grouper-dev] ldappc <include file=ldappc-other.xml /> ?


Any advice/comments on including another xml file within ldappc.xml ?


e.g. <include file="ldappc-server-config.xml" />


Having a separate config file containing ldap connection information would make it easier to run tests, to run ldappc for different provisioning situations, and it would be easier to share ldappc.xml examples sans private authentication credentials.


I haven't found anything which enables <include /> in commons-digester parsing, yet. Otherwise it could be manually coded.




Archive powered by MHonArc 2.6.16.

Top of Page