TypeMappings for wrapped primitives do not need 'java.lang.' qualifier, should
be able to use standard UML datatypes, add additional datatypes
----------------------------------------------------------------------------------------------------------------------------------------------
Key: UMLMETA-99
URL: http://jira.andromda.org/browse/UMLMETA-99
Project: UML Metafacades
Issue Type: Improvement
Affects Versions: 3.4-SNAPSHOT
Environment: andromda 3.4
Reporter: Bob Fields
Assignee: Bob Fields
Priority: Minor
Fix For: 3.4-SNAPSHOT
Change <to> TypeMappings for standard types from java.lang.X to X, in order to
make output code smaller and more easily readable. Model <from> datatypes
should include PrimitiveTypes::, UML2::, UMLTypes::, UMLPrimitiveTypes:: (if
they exist), in addition to the current datatype::. This requires mapping back
from the unqualified type to the java.lang. qualified type for places where
reflection is used such as Spring/Hibernate/EJB XML mapping files. It also
requires additional checks to be made when doing something like ($variableName
== 'java.lang.Character') in the templates or in the java implementation code,
to either check for the additional unqualified types or to use the
Classifier.isXXXType methods. OCL validations generation should also use
unqualified types in the generated code, and should also be output on multipile
lines for readability.
Add datatypes for Set, SortedSet, Map, SortedMap etc, with a mapping to the
default implementation types for Collection/List/Set/SortedSet based on
unique/ordered UML properties. Add default implementationType mapping for each
of the declaration types (i.e. List -> ArrayList, SortedSet -> TreeSet) to
avoid hard-coding the implementation types. Ensure results are consistent for
environments where ordering/unique is not taken into account, such as XML
binding (default to List/ArrayList for everything). Add datatype for Money,
mapping to BigInteger, in order to avoid rounding errors that occur with
decimal datatypes used for financial transactions.
--
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
