Hi, I'm not sure that I understand what you want to do. When you create a descriptor for a component e.g. using createEngineDescription(…), this descriptor is configured with the default values (unless you override them in the call to createEngineDescription).
You can change parameters on such a descriptor using ResourceCreationSpecifierFactory.setConfigurationParameters(…) Does that help? Can you make a more vivid example of what you are trying to accomplish, maybe with a bit if pseudo-code marking those places that remain unclear how to handle them? Cheers, -- Richard On 27.11.2013, at 07:47, 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
