Remove or weaken the constraints on Java's generated enumeration value types #1084
Description
However, some message attributes are defined using relatively loose types for strong compatibility. For example, the transaction type is defined as short, but its actual value may only be a limited set of values.
In Java, setting or identifying the appropriate value can be confusing without the assistance of enumeration types.
Currently, if a defined enumeration type is not used in a message, sbe-tool will not generate Java code.
Is it possible to remove this constraint, or make it a configurable option?