Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
The mandatory flag on configuration parameters indicates if the target field accepts a null value or not. For primitive fields, this is obviously not the case. Thus, for primitive fields, mandatory must always be true and if we want to avoid that the user actually has to specify the parameter every time, the defaultValue must be set. That makes the parameter effectively optional from the user's perspective.
Probably the best place to catch this is the "generate" or "enhance" goal of the Maven plugin - which could immediately fail.
It could also be detected by uimaFIT itself at runtime, but then it would be better just to warn (maybe warn less with high frequency).