Message-ID: <965141247.40706.1371618480320.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_40705_1708384691.1371618480320" ------=_Part_40705_1708384691.1371618480320 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Following MODELLO-26, here is a proposal (und= er construction) for Enumeration Handling in MODELLO.
Alternativly, we could consider that the value is a java only indication= and put that in java metadata. That would lead to a more compact declarati= on:
But that would be a correct notation only if the actual values of the en= umeration could be considered an indication for the Java plugin only.
The above model should lead to a Java class, like:
now, question is, where to check for model integrity?
Should we provide a setter (setEnumeration) which would require the para= meter to be one of the possible values? Like:
Or just a plain setter, the integrity being the work of the parser. I gu= ess first solution is more interesting....
Now, when it comes to parsing, how should we handle it? Just pass down t=
he value to the setter, and see if it is ok with the value?
Should we provide support (in the xml file) for both the keys and the value= s?
Say, with the continuum-model:
Do we want to be able to handle
in the data?
This question is a central one, since, most of the other plugins (xml pa= rsers, xdoc, xsd) will depend on this question...
So waiting for someone to provide an answer there------=_Part_40705_1708384691.1371618480320--