Add ClassifierFacade additional datatype checks,
ModelElementFacade.documentationPresent, reservedWord, naming convention checks
--------------------------------------------------------------------------------------------------------------------------------
Key: UMLMETA-98
URL: http://jira.andromda.org/browse/UMLMETA-98
Project: UML Metafacades
Issue Type: Improvement
Affects Versions: 3.4-SNAPSHOT
Environment: Andromda 3.4-SNAPSHOT
Reporter: Bob Fields
Assignee: Bob Fields
Priority: Minor
Fix For: 3.4-SNAPSHOT
Additional datatype checks and documentationPresent could simplify the code in
some of the templates, and make transition to unqualified java.lang. datatype
declarations easier. Checks for reserved word usage can prevent invalid
uncompilable code from being generated by modelers who do little development
work. Optional naming convention checks can check for things like classes
without initial Caps, operations without initial lower case (should not apply
to dotNet code generation), static final variables not in UPPERCASE, etc.
Implementation would have to be turned off for metafacade generation because a
number of reserved words are used and qualified with get/set/is such that no
reserved word violation occurs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.andromda.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
