UIMA already checks that the definition of a parameter matches that of its setting, so this would be an analogous check that the use of the parameter in the annotator also matches. It would make for safer & cleaner code if the mandatory, multivalued. and type attributes could be checked by these methods, throwing an error much as the framework does on descriptor errors.
On Thu, Sep 19, 2013 at 4:06 AM, Jörn Kottmann <[email protected]> wrote: > On 09/18/2013 04:34 PM, Alexandre Patry wrote: > >> From what I understand, the root of the problem is the lack of a >> versioning mecanism for analysis engines. The best solution from my point >> of view would be to recommend a way to version analysis engine and offer >> new methods to UimaContext to access configuration parameter by type, but >> without the `mandatory` argument which repeats what is in the descriptor. >> > > A user can also accidentally change the descriptor, then the AE code would > fail again in the ugly way if there > are no additional checks to make it fail nicely (not by throwing NPEs, or > ClasCastExceptions). > > Jörn >
