Additional validations to ensure primitive/wrapped datatype is consistent with
multiplicity lowerBound
------------------------------------------------------------------------------------------------------
Key: UMLMETA-97
URL: http://jira.andromda.org/browse/UMLMETA-97
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
If using XML Bindings with generated code, there is no distinction between
primitive and wrapped types, only multiplicity is used when converting from
Java -> XML -> Java. In order for round tripping to be consistent, wrapped
types should always have lowerBound = 0, and primitive types should always have
lowerBound > 0. If lowerBound not specified in the model, value should default
to 0 or 1 based on the primitive/wrapped datatype, otherwise to the global
default (current functionality). Also, identifier attributes created
dynamically for entities should be wrapped optional lowerBound=0, not require
lowerBound=1, since the identifier value is typically populated during insert.
--
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
