[Building Sakai] Best way to add properties files?

[Ray Davis]

Option 1 is what the sakai-configuration.xml file was put there to 
support, so you might as well trust it. :)  The way the current design 
prevents such conflictd is by letting you specify a "parent" for your 
own list of properties files, as described at
http://confluence.sakaiproject.org/display/REL/More+Flexible+Sakai+Configuration

     <bean id="org.sakaiproject.component.SakaiProperties"
       parent="org.sakaiproject.component.DefaultSakaiProperties">

If future releases need to fiddle around with the built-in list of 
properties files, they'll do so in "DefaultSakaiProperties" and not 
interfere with your local list. And if some future developer *does* 
happen to break SAK-8315 behind our backs, that would be considered a 
bug and would have to be fixed (hopefully before a official release 
happened).

Best,
Ray

On 8/12/09 11:59 AM, Joshua Swink wrote:
> What is the best way to add properties files to be read when Sakai starts up?
> 
> I see two options:
> 
> 1) Put a sakai-configuration.xml file in $CATALINA_HOME/sakai, and add
> a properties filename to it
> 2) Modify sakai-configuration.xml in the source, and add a properties
> filename, and redeploy Sakai
> 
> The downside of the first method is that if a future release adds a
> config file to the sakai-configuration.xml file in the source, that
> change will have no effect because I overwrote the whole bean. And
> there won't be any explicit indication that this has happened.
> 
> The downside of the second method is that this is a source change that
> I'll have to keep track of whenever I synchronize our source with a
> new release of Sakai.
> 
> It would be best if there were some way, in a file in
> $CATALINA_HOME/sakai, to add new property filenames to the list,
> without overwriting the default list. But I can't see how to do that
> just now. So the best way appears to be the second method - change
> sakai-configuration.xml in the source, since silently missing
> potential future configuration files is not the kind of trouble I want
> to face in the future.
> 
> Josh
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
>