When applying the Java Naming Conventions (case-insensitive by design) to case-sensitive input, result will be clashing definitions. The attached test case shows this for e.g. the input 'm' vs 'M' (in the light of prefixes aka milli and Mega), whose generated enum symbols will both be 'M', therefore producing a clash (and error).
It shouldn't generate an uppercase 'm' for the input string 'm' in the first place.
This issue shall serve both as a reminder to the castor team that xml is case-sensitive as well as giving Werner a place to attach a potential fix to (as talked about on the -user mailinglist).