
fUML Reference Implementation v0.4.0 now available for download! | Foundational UML Reference Implementation
fUML Reference Implementation v0.4.0 now available for download!
Version 0.4.0 of the fUML Reference Implementation is now available for download here. This release is consistent with the Beta 3 specification (not yet publicly available) produced by the fUML Finalization Task Force (FTF), which is the finalized spec for fUML 1.0. In addition to the issues resolved in v0.3.0, it incorporates resolutions to the following OMG issues, as adopted by the fUML FTF:
- Issue 13881: Subclause: 8.5.2.2.6 ActivityParameterNodeActivation
- Issue 14545: Variable needs initialization in InputPinActivation::receiveOffer
- Issue 14547: Structured activity node execution model needs to be corrected
- Issue 14618: ObjectNodeActivation::unofferedTokens is spurious
- Issue 13453: ExecutionFactory::instantiateVisitor should not use Java reflection
- Issue 14533: Include activity diagrams for classifier behaviors
- Issue 14550: Revise fUML to be based on UML 2.3
- Issue 14990: Values passed out to pins from empty parameter nodes
- Issue 14992: UML input pins do not accept more tokens than their actions can immediately consume
- Issue 15088: Additional changes required for structured activity node execution
- Issue 15089: Modification to AcceptEventActionActivation
- Issue 15090: Error in ObjectActivation::dispatchNextEvent
- Issue 15094: Additional changes required for action firing semantics
(Issues 13167, 14533 and 15127, also resolved by the FTF, did not impact the XMI or execution implementation.)
In addition:
- Routed fUML.Debug messages to the log4j log, which is no longer printed to the console by default, except for a limited number of execution "event" messages, which are printed directly to the System.out.
- Fixed OMG Issue 15130: An action may not stop firing again, even though this has not yet been formally resolved by the new fUML 1.1 Revision Task Force (RTF).
The execution engine in this version is final for fUML 1.0. However, fUML 1.0 is now based on UML 2.3, and the XMI loader has not yet been updated to properly handle all the metamodel changes for UML 2.3. A new loader framework is under development that will be based directly on the fUML 1.0 abstract syntax metamodel, as updated for UML 2.3. When this development is complete, the new XMI loader framework will be included in the next release, which is planned to be v1.0.0.

rss

