Aaaah.... "Context Fragments"... that's exactly what I needed. Not sure how I missed that whole organizational thing, I remember reading that phrase but for whatever reason it didn't strike me as what I needed. But yes, that works well and allows me to simply distribute my custom context files from cfengine over to the dspace server.
One last thing I'm puzzled about. Is there a way to do something similar with <Connector> definitions? The Ubuntu/tomcat6 install comes with the AJP connector line commented out. I can get cfengine to edit the file and put that line in the right place, but it's fiddly and not particularly robust. Much better would be if I could do something similar to the context fragments and just plop a "local_connectors.xml" file somewhere. One last question... I may have missed a source of docs, but in the dspace documentation I've been reading (mostly wiki.duraspace.org and random googled blogs and pages) I have not yet run across the information we've covered above. Is there another location I should be looking at? Thanks again... this really helped me get up and running. -glenn ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
