data about via brittle &amp; 
breakable POJO signatures, that we instead use a tagged-data 
value-approach? By using enumerations, might we be able to create an 
object that will neither break over time, nor create queer 
signature-dependencies throughout our applications? Even when adding (or
 removing!) those data-laden getters &amp; setters?<br><br><h2>ENumerated Java Objects (ENJO)</h2><br>Consider what happens when we combine the POJOs 'getters and 'setters with Java's Enumeration.<br><pre>public 