|
| 1 | +### fUML Reference Implementation |
| 2 | +### v1.2.0 Release Notes |
| 3 | + |
| 4 | +This is a base release of the fUML Reference Implementation, conforming to v1.2.1 of the [fUML Specification](http://www.omg.org/spec/FUML/1.2.1). |
| 5 | + |
| 6 | +### fUML Execution Engine |
| 7 | + |
| 8 | +This is a new base release of the fUML Execution Engine. It includes all implementation updates from [v1.1.4](./fuml-1.1.3.md) and previous |
| 9 | +releases tracking the issues resolutions adopted by the fUML 1.2 Revision Task Force (RTF). The complete set of resolved issues implemented |
| 10 | +since the v1.1.0 base release are listed below. The full list of remaining open fUML issues is available at http://solitaire.omg.org/issues/task-force/FUML13. |
| 11 | + |
| 12 | +The following issue was resolved as an "urgent issue" by the fUML 1.3 RTF, resulting in the formal release of fUML 1.2.1 rather |
| 13 | +than fUML 1.2: |
| 14 | + |
| 15 | +[FUML 13-12](http://issues.omg.org/issues/task-force/FUML13#issue-38461) Bad event accepter removed from the waitingEventAccepter list |
| 16 | + |
| 17 | +The following issues were resolved by the fUML 1.2 RTF: |
| 18 | + |
| 19 | +[FUML 12-7](http://solitaire.omg.org/issues/task-force/FUML12#issue-16432) (18279) ReclassifyObjectAction does not preserve structural feature values |
| 20 | + |
| 21 | +[FUML 12-8](http://solitaire.omg.org/issues/task-force/FUML12#issue-16433) (18280) LoopNodeActivation does not currently handle the firing of a contained activity final node |
| 22 | + |
| 23 | +[FUML 12-9](http://solitaire.omg.org/issues/task-force/FUML12#issue-16434) (18282) The bodyOutputLists for a loop node need to be cleared when the node fires again |
| 24 | + |
| 25 | +[FUML 12-10](http://solitaire.omg.org/issues/task-force/FUML12#issue-16435) (18321) Certain Boolean flags are not properly initialized in some cases |
| 26 | + |
| 27 | +[FUML 12-11](http://solitaire.omg.org/issues/task-force/FUML12#issue-16436) (18362) Problem with ActivityExecution::terminate |
| 28 | + |
| 29 | +[FUML 12-12](http://solitaire.omg.org/issues/task-force/FUML12#issue-16437) (18364) RealValue::toString puts too many digits in the mantissa |
| 30 | + |
| 31 | +[FUML 12-13](http://solitaire.omg.org/issues/task-force/FUML12#issue-16438) (18365) Objects with cyclic references cannot be converted to string representations |
| 32 | + |
| 33 | +[FUML 12-14](http://solitaire.omg.org/issues/task-force/FUML12#issue-16439) (18508) FoundationalModelLibrary, UnlimitedNaturalFunctions: inconsistencies between the spec and the normative xmi |
| 34 | + |
| 35 | +[FUML 12-15](http://solitaire.omg.org/issues/task-force/FUML12#issue-16440) (18510) ListFunctions should have a ListConcat behavior |
| 36 | + |
| 37 | +[FUML 12-16](http://solitaire.omg.org/issues/task-force/FUML12#issue-16441) (18511) The ReadLine::result parameter should have direction "return" |
| 38 | + |
| 39 | +[FUML 12-17](http://solitaire.omg.org/issues/task-force/FUML12#issue-16442) (18512) FoundationalModelLibrary::Common::Notification should be public |
| 40 | + |
| 41 | +[FUML 12-18](http://solitaire.omg.org/issues/task-force/FUML12#issue-16443) (18513) The Listener reception of Notification should have a name |
| 42 | + |
| 43 | +[FUML 12-19](http://solitaire.omg.org/issues/task-force/FUML12#issue-16444) (18514) The types of the ReadLine::errorStatus and WriteLine::errorStatus parameters should be Status |
| 44 | + |
| 45 | +[FUML 12-20](http://solitaire.omg.org/issues/task-force/FUML12#issue-16445) (18529) Feature values need to be created for private structural features of parent classifiers |
| 46 | + |
| 47 | +[FUML 12-21](http://solitaire.omg.org/issues/task-force/FUML12#issue-16446) (18693) ReclassifyObjectAction handles removal of structural features incorrect |
| 48 | + |
| 49 | +[FUML 12-22](http://solitaire.omg.org/issues/task-force/FUML12#issue-16447) (18714) RemoveStructuralFeatureValueActionActivation: Determination of position(s) of value to removed results in inf. loop |
| 50 | + |
| 51 | +[FUML 12-23](http://solitaire.omg.org/issues/task-force/FUML12#issue-16448) (18721) RemoveStructuralFeatureValueAction: Removal of links with specified remove at value works incorrectly |
| 52 | + |
| 53 | +[FUML 12-24](http://solitaire.omg.org/issues/task-force/FUML12#issue-16449) (18722) RemoveStructuralFeatureValueActionActivation: Removing links with specified remove at value works incorrectly |
| 54 | + |
| 55 | +[FUML 12-31](http://solitaire.omg.org/issues/task-force/FUML12#issue-16456) (18800) Correction of method UnlimitedNaturalValue.equals |
| 56 | + |
| 57 | +[FUML 12-33](http://solitaire.omg.org/issues/task-force/FUML12#issue-16458) (19008) Extensional values should have an unique identifier |
| 58 | + |
| 59 | +[FUML 12-34](http://solitaire.omg.org/issues/task-force/FUML12#issue-16459) (19528) AcceptEventActionActivation::match should match instances of descendants of a trigger's signal |
| 60 | + |
| 61 | +[FUML 12-35](http://solitaire.omg.org/issues/task-force/FUML12#issue-16460) (19679) Initial execution of an activity is not run-to-completion |
| 62 | + |
| 63 | +[FUML 12-36](http://solitaire.omg.org/issues/task-force/FUML12#issue-17283) (19130) Problem with CallActionActivation: Possible infinite loop in removeCallExecution() |
| 64 | + |
| 65 | +[FUML 12-57](http://solitaire.omg.org/issues/task-force/FUML12#issue-37808) List parameters of ListFunctions should be non-unique |
| 66 | + |
| 67 | +### XMI Loader/Infrastructure |
| 68 | + |
| 69 | +This base release includes all updates from [v1.1.4](./fuml-1.1.4.md) and previous maintenance releases. |
| 70 | +There are no further changes to the XMI Loader in this release. |
| 71 | + |
| 72 | +#### Bugs |
| 73 | + |
| 74 | +None |
| 75 | + |
| 76 | +#### Improvements |
| 77 | + |
| 78 | +None |
0 commit comments