Just in case you haven't considered it, version 2.4.2 has a new option for overriding configuration parameters outside of component descriptions, called external overrides. It is implemented via an additional settings file. Component descriptors remain static, like code, which would work well for PEAR packaged components.
More details at http://uima.apache.org/d/uimaj-2.4.2/references.html#ugr.ref.xml.component_descriptor.aes.external_configuration_parameter_overrides Eddie On Wed, Nov 27, 2013 at 4:47 AM, Jens Grivolla <[email protected]> wrote: > Hi, > > so far we were using PEARs to manage different configurations of > components, e.g. having a CountryMapper, CityMapper, PersonMapper, etc., > all based on ConceptMapper but with different settings/models. > > How would I do that in uimaFIT? Basically I would like to create > components that just override the default values for parameters/resources. > > In some cases, parameters are additionally overridden at the pipeline > level (CPE/uimaFIT), e.g. when using a database CasConsumer where we would > have several base configurations (e.g. annotation to DB column mappings), > but then override the DB connection settings in the pipeline. > > Having the full configuration at the pipeline level makes it much more > difficult to manage configurations, so I would like to be able to point to > a given component and automatically get the correct default settings. > > Thanks, > Jens > >
