Re: [loom] properties in configuration

peter-4lf8KW9E9MLMqX/[email protected] wrote:

>Hiya,
>  
>
>Basically what it does IIUC is grab a config.properties from base directory
>of .sar and use that to interpolate the SAR-INF/config.xml. My initial
>reaction is that the config.proeprties should be in SAR-INF/ directory.
>Anyone else have any opinions?
>
>  
>
SAR-INF/ sounds fine.  In addition, this allows the container to define 
properties for the configuration files.  Currently, the container just 
(hardcoded) creates two properties app.name and app.path.  In the 
future, it could be possible to manage the properties automatically set 
by the container using JMX or something.  When I get a few minutes I 
might take a second pass at this with that in mind.

>As for unit testing my initial reaction would to be just unit test the
>methods you over-rode. ie Only unit test processValueText,
>processAttributeText and expandProperties.
>
>Then later on when we do integration unit testing we write a block that
>epects certain values in its context. These would only be accessible via
>interpolation and thus the unit test would start u[p component and read
>values and except if non matching.
>
>  
>
I like that.

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net