These are the bugs that have been resolved in MetaModelAgent v4.3.0 or newer, any remaining open bugs can be found in the list of open bugs.
These are the bugs that have been resolved in MetaModelAgent v4.3.0 or newer, any remaining open bugs can be found in the list of open bugs.
Literals get in some circumstances moved from property default value when creating a new slot based on the property
| This happens when the model is using a user defined type library for primitive types.
The workaround is to replace the default value in the add slot wizard by another value and then afterwards change back to the default value
Unnecessary profiles are added when creating a new model if referred from external metaclass
|If a metamodel contains metaclasses defined as external that refers a stereotype from a profile, that profile will be applied to the model being created using the MMA New Model wizard, even if the profile is not to be used within the model|
|4.2.2||MMA-1834||Model Reporting, Papyrus||
Line breaks in comments representing documentation are not respected in web publish output
| New lines added to the documentation field are not respected in web publish output.
The documentation is presented without any new line or paragrah separators.
|4.2.2||MMA-1825||Papyrus, UI Wizards||
MMA switches association source and target ends in diagrams
| When adding an association using MMA Add WIzard in a diagram, the labels of the association ends are switched in the diagram. However the role ends in the model will be correct.
The work around is to remove the association manually from the diagram and redraw it using drag and drop from model explorer.
Hyperlinks are invalidly provided to unpublished guideline pages in nested element sections
|If the web publish setting is to not publish guideline hyperlinks, hyperlinks are created anyway in the nested element sections in web published model report. Those hyperlinks will then lead to unpublished guideline pages.|
|4.2.2||MMA-1811||Guideline Reporting, Model Reporting||
Web publish output does not support older vesions of Internet Explorer
|The web-publish output renders incorrect in older versions of Internet Explorer. E.g. older than IE11|
|4.2.2||MMA-1804||Papyrus, UI Diagram & Palette||
Switched association end details may occur on diagram when using MMA Add Wizard
| Association end details (role name and multiplicity) will occasionally be placed on the wrong side of the association, when the association is created by selecting the two elements and using the MMA Add Wizard.
It seems to occur randomly.
The work around is to remove the association from the diagram and drag&drop in again onto the diagram from the model explorer.
Metamodel could sometimes not be activated towards metametamodel if it contains severe errors
| This occur first time a metamodel is validated in a new modeling tool session or every time if the current license is limited (e.g. FREE or BASIC).
The activation fails if the metamodel contains a metaclass without a MMA-stereotype or if it contains invalid metaclass attribute names
By making sure that each class in the metamodel has a proper MMA-stereotype and that the attributes has proper names, the activation will work.
|4.2.2||MMA-1791||General UML guidelines, Papyrus||
State machine diagrams are not allowed within States when using the General Modeling Guidelines
|States must be able to hold state machine diagrams and state machine diagrams must be able to have a state as their root element. This is needed to support PapyrusRT model structure. This will be fixed for Papyrus 3.0 only|
|4.2.2||MMA-1783||Model Reporting, UI Property View||
Multi-valued properties of element types are not read correctly
| Multi-valued properties which type is model elements (except instance specifications) are not read correctly and therefor not presented in the property view nor published in web publisher
This bug was introduced in 4.2.1 when solving bug MMA-1746
Static diagrams added using the add wizard are prefilled with the element owning the diagram
|This bug was introduced in MMA 4.2.1 003 public release.|
Exception sometimes occur in connection wizard search mode
|It seems to occur only when a metamodel have been moved to a new project or the project or metamodel have changed name.|
|4.2.2||MMA-1770||Papyrus, UI Wizards||
Searching for metamodel in Connection wizard leads to absolute file reference in model
| If the model is connected to a metamodel using the connection wizard and a search is made for available metamodels in the workspace, the resulting reference will be an absolute file path.
Workaround is to load the metamodel using the "Import->Import Package From User Mode" context menu entry, followed by opening the connection wizard again, where the loaded metamodel should be available in the drop-down menu.
Exceptions are thrown if a metamodel uses enumerations without any literals
|This may also occur if an enumeration literals refers to external files that does not exist.|
|4.2.1||MMA-1762||Papyrus, UI Wizards||
Models created in nested folders using MMA create model wizard is being corrupt
| When creating a model in a nested folder in a project, a popup-dialog appear saying that "your model is corrup, invalid links have been found".
The workaround is to create the model in the projectÂ´s root folder and then afterwards move the model resources into the subfolder.
|4.2.1||MMA-1760||Guideline Reporting, Papyrus, UI Guidance View||
Custom icon presentation fails sometimes if metamodel specifies several stereotypes for an element
| If a metamodel contains a metaclass that requires more than one mandatory stereotypes, Custom-defined icons for the stereotypes may not be shown in the MMA Guidance View and generated guidelines web.
The bug is only visual and does not affect creating or editing models using MetaModelAgent
PrintOut function does not respect preference settings nor licens mode
| The print out features does not respect hide fixed property setting and the license mode.
It does not either sort the properties in alpabetic order.
|4.2.1||MMA-1754||UI Property Table View||
Integer property values are sorted in alphabetic order in MMA Property Table View
Externalized metamodel enumeration literals are not sorted correctly
|The literals within an externalized file are expected to show up in the same order as defined and not in alphabetic order|
"Hide fixed values" setting in web publish is not respected
|The setting "Hide fixed values" which should control wheter fixed key property values should be published or not does not work. Fixed key properties are published even if this setting is chcked. This bug seems to have been introduced in v4.2.0.|
|4.2.1||MMA-1746||Model Reporting, Model Validation, UI Property View||
Multi-valued property values of primitive types is not retrieved from model
|Multiple valued property values are not read correctly from model. This affects the MMA Property View, Model validation and model publishing. This bug seems to have been introduced in MMA v4.1.4|
Each diagram heading is listed once more without content on the web publish print-out page
|The print out page of a published model contains an extra list of diagram headers at the end of each section. This also holds for diagrams in nested elements|
|4.2.1||MMA-1743||UI Property View||
Exception thrown when showing an association with undefined end in the MMA property view
|4.2.1||MMA-1739||General UML guidelines||
Metaclasses with @SUPER keyword as part of the documentation may accidentally include the description of a constraint
| Metaclasses that has @SUPER keyword as part of the documentation will incorrectly include the description of a constraint if they can hold constraints and there is no explicit constraint definition in the metamodel
This holds for some metaclasses even in the General UML Guidelines, for example OpaqueAction
|4.2.1||MMA-1738||Model Reporting, Papyrus||
Hyperlinks added to elements in a diagram are not available if the element is outside the publishing scope
|4.2.1||MMA-1737||Model Reporting, Papyrus, UI Others||
Property value-controlled stereotype icons in Papyrus is not supported
| A stereotype in Papyrus may have several icons defined, A boolean expression refering to stereotype properties stored in each image/icon element controls if the icon should be used or not.
This behavior should be supported in the UI and web-publish result of MMA.
|4.2.1||MMA-1736||UI Property View||
Exception sometimes occur when switching to current activation in element selection dialog
|This seems to occur if there is no currently selected element and no selectable element either|
|4.2.1||MMA-1732||Model Reporting, Papyrus||
Hyperlink hovering popup does not always close when exiting the popup area
|Sometimes you must move the cursor far below the popup hover window to Close it. The problem is related to an incorrect CSS-setting|
|4.2.1||MMA-1728||UI Property View||
Rich-text widget content does not updates automatically when the popup-editor is in plain-text mode
|If the widget presenting documentation is a rich-text widget (i.e embedded web browser) and the popup dialog editor is a plain-text editor, the content of the rich-text editor will not update automatically when the popupdialog is closed. However the edited text is stored in the model even if it is not displayed in the rich-text widget|
|4.2.1||MMA-1714||General UML guidelines, Metametamodel, Papyrus||
Diagram root element property not respected by MMA diagram palette
| The root element property of a diagram in Papyrus, Controls where elements added using the palette are created.
MMA does not respect this property. Currenttly, elements added using the MMA palette is created within the owner of the diagram.
|4.2.1||MMA-1669||General UML guidelines||
Actions are not allowed in Interactions
| When using the built-in General UML Guidelines, errors are reported in MMA Problem View for actions nested in Interactions
Actions can neither be added to interactions when using a custom metamodel
|4.2.1||MMA-1395||Guideline Reporting, Papyrus||
Stereotype icons are not always published when doing "Publish Guidelines" if the profile is not already loaded in the same editing domain
|The workaround is to do the guideline reporting through the model reporting|
|4.2.1||MMA-1328||Papyrus, UI Wizards||
Behavior diagrams cannot be created within structured classifiers
| When a behavior diagram is added to a structured classifier, the diagram is created but a strange Icon is displayed in the model Explorer.
One reason may be that the context is not set.
Therefore addition of behavior diagrams to structured classifiers have been revoked from MMA.
"Continue after error" preference setting behavior does not respect classifier childs
| If the setting is true, any package hiearchy is parsed for nested classifiers. All packages in the hierarchy may be considered unknown and parsing will still continue.
Classifier hierarchires are however not further parsed, even when the setting is true.
If the setting is false. all nested packages are invalidly reported as unknown packages. Nested packages should not be parsed.
The expected behavior should be consistent when both package and classifier hierarchies are parsed. .
|4.2.1||MMA-1240||Model Validation, UI Property View||
@INSTANCE keyword in property definitions is not respected when the type is a primitive type
|For example in attributes: The default value shall comply to the type, e.g. only true and false are valid for Boolean type.|
State machine diagrams created by MMA gives exceptions when editing afterwords
|State machine diagrams created by MMA contains a state machine that gives exceptions when resized. The diagram is not completly created.|
Diagram is not correctly deleted when removed using quick fix in Problem View
Enumeration with only one literal in the metamodel invalidly results in an editable text widget in wizards and property views
Loaded models deployed in a plug-in may be activated by MMA
| It should not be possible to activate a model that is deployed in a plugin in RSA.
This is a correct behavior in Papyrus as the loaded model is visible in the model explorer
Changes in the metamodel is not reflected when re-activating MMA by use of the tool button in the tool bar
|Reactivation MMA by use of the tool button in the tool bar should result in an activation using a re-parsed metamodel.|
|4.2.0||MMA-1726||UI Property View||
Clicking on a problem in the MMA Problem View will update the MMA property View incorrectly
| (Resolved in v4.2.0 build 008)
Clicking on a problem in the MMA Problem View will update the MMA property View incorrectly, the view will not be set to empty before being refreshed. Clicking on an element somewhere else in the workspace will restore the MMA Problem View correctly.
|4.2.0||MMA-1725||UI Problem View, UI Property View||
Closing the MMA Property View will give exceptions when clicking on a problem in the MMA Problem View
| (Resolved in v4.2.0 build 008)
The bug occurs only when the MMA Property View (not the standard property view) is open and then is closed.
When clicking on some of the problems in the problem view after the MMA Property View has been closed, an exception is raised.
The only way to avoid these exceptions when clicking on a problem will be to restart the Papyrus session.
As long as the MMA property view is not closed during the session (or not opened at all) the exception will not occur.
This bug does not affect the usage of the standard property view at all. The only way to get the exception is to close an already opened MMA Property View.
"No more handles" exception is thrown after some time of running MMA functionality
|There are memory leaks related to the usage of the SWT-library.|
|4.2.0||MMA-1697||Papyrus, UI Others||
Enumerations and Primitive types could not be added to profile diagrams using MMA Quick fix
|4.2.0||MMA-1696||Papyrus, UI Others||
Interfaces could not be added to component diagrams using MMA quick fix
|4.2.0||MMA-1695||Papyrus, UI Others||
Models could not be added to diagrams using MMA quick fix
Missing icon for Start Object Behavior Action
NLS warning messages appear when starting MMA
|NLS warning messages appear in some environments and circumstances when starting MMA|
|4.2.0||MMA-1683||Papyrus, UI Others||
MMA not consistent with Papyrus stereotype icon presentation principle
| Papyrus Always displays the Icon from the first applied stereotype. If the first stereotype have no Icon associated, the standard Icon is displayed.
MMA displays the Icon from the first applied stereotype that has a defined Icon. If none of the applied stereotypes has an Icon, the standard Icon is displayed.
|4.2.0||MMA-1682||Papyrus, UI Others||
Package Diagrams cannot be created using MMA Add wizard in Papyrus 2.0
|When trying to create a package diagram using the Add Wizard, a class diagram is being created. This problem is limited to Papyrus 2.0 only.|
Large models and limited memory on 32bit hosts may result in out of memory when publish model report
|The model reporting feature will stop when publishing the print out page. THe property reference pages will then not be published|
|4.2.0||MMA-1673||Model Reporting, RSA||
Foreign (non-UML) elements on UML diagrams may throw exception in Web publisher
|This holds for example for Java-classes that have been dragged&dropped into class diagrams.|
|4.2.0||MMA-1671||UI Property View||
Changing the value of a literal creates a new literal
| Changing a literal value results in a new literal being created. All properties of the existing literal will be lost.
The correct behavior should be that the same literal element should be kept and only its value should be changed, as long as the new value results in the same kind of literal.
Extensions are incorrectly identified as associations
|When activating MMA for a UML profile: Extension relationships between a stereotype and a UML metaclass is invalidly identified as an association instead of as an extension.|
The bugs in the list are all reported and confirmed. Any major bug will be resolved in the next upcoming release.
|MMA-1803||Model Validation, UI Property View||
Lower limit of multi-valued user defined properties are not validated
|A lower limit of 1 for example is not reported as invalid, not by color in the MMA Property view or by an entry in the MMA Problem View|
|MMA-1793||Model Reporting, PapyrusRT||
Fallback filenames are used for some RT-elements when publishing an PapyrusRT model using PapyrusRT RCP
| The standard way to retrieve the UUID, Resource.getURIFragment(element) does not work for all RT-specifik element types when running the RCP-installation of Papyrus.
If so, files with encryptic file names are generated instead of UUID-based file names.
An invalid thread access exception occurs first time an unloaded profile is refered
|This exception does not affect the resulting guideline web.|
|MMA-1748||Model Reporting, Papyrus||
Invalid thread access exception sometimes in web publish
| Invalid thread access occurs sometimes when executing web publisher. This seems to occur randomly. A temporary fix has been made by catching the exception, but this bug is still open waiting for a permanent fix.
Work around that have proven successful is to restart the tool and redo the model pubslishing.
Publish documentation failure sometimes when reusing output folder
| Exceptions has been detected a few times when publishing once more into an existing folder. This have not been reproducable in test environments.
Work around may be to clean the target folder or use another target folder.
The order of ordered nested elements are not preserved in web publish
| The order of parameters are semantically significant and must be preserved. The same is for Pins and for nested properties (e.g. qualifiers)
These elements should therefor always be listed in original order as stored in the model.
Inherited elements from other activations are presented with the other activationÃ‚Â´s metaclass
| If an element inherit another element, for example a property, the other element has a metaclass from the metamodel from the other activation.
In such a case the element should be presented in some special way
If both the activations uses the same metamodel, the elements shoould be grouped under the same heading in the nested element section.
The preference setting "Show only editable pages in wizards" is not respected for the first Add wizard page
|Add wizard should not be showned when adding an element or relationships by selecting two elements, if there are no editable properties and the preference setting is set to hide non-editable pages.|
|MMA-1539||Model Validation, Papyrus||
Associations are reported as invalid elements if there are permitAll operations allowing any association ends
| To remove the invalid reported problem, a manual refresh (reactivation) must be made.
Even afterwards and also in RSA when selecting such an association, a message in the GuidanceView says that the element could not be identified
Metaclass comparison reports invalid errors when constant default values are used in combination with enumeration types in metaclass attributes
| When two metaclass attributes are compared and they have different fixed default values but the same enumeration as types. They are invalidly reported as overlapping as the default values are not respected.
The bug is related to the compareEnumTypes() method in class MetaClassComparison
Adding a Capsule using RSA RTE UI when Change Wizard is enabled causing an "Invalid model modification" dialog to appear
| Adding a Capsule using RSA RTE UI automatically add some nested elements as well.
This is very difficult to fix because the EMF Transaction framework reports the added elements in a reverse order, making it impossible for MMA to identify the added elements correctly.
One solution would be to detect that there is nested elements to a capsule being created and disable the change wizard upon this fact.
This behavior may occur in other situations as well where several elements are added using a single operation.
|MMA-1241||UI Property View||
Item selection dialog button for Slot value property need sometimes to be pressed twice before the dialog appear
| If the defining feature has been changed the item selection dialog for slot value has to be pushed twice
The problem occur because the widgets are redrawn when the defining feature lost focus. At that point the push button listener is not yet registered.
Automation is not always automatically enabled on a model that have been created
| When a model is created and MMA has the preference setting "Always activation". MMA tries to do the activation Before the editing domain is available. Automation is therefore not initialized. Activation must therefore be made manually.
The stereotype 'templatebinding' in the MMA-profile used in metamodels is misspelt
|The correct name should be 'templateBinding' with an uppercase B.|
MMA Property View is not automatically updated when a property value is changed in some other view or editor
|An automatic update would be the expected behavior But that may make the MMA Property View obsolete if it affects key-properties. In such a case the classification might change forcing a complete switch of the view content or that the view should be empty (base on that the element could not be classified). This bug needs more investigation and consequence analysis.|
Circular <<key>> references in a metamodel leads to an inifinte loop upon activation
|This might be detected if a test model can be automatically genererated from a metamodel|
UML Connectors could not be created using the General UML Guidelines
| The current UML General Guidelines does not have 2 as a lower number of Connector Ends to a connector, that means that a connector will be created by the Add-wizard without the option to create any connector ends. That results in an thrown RSA exception.
The lower number of Connector Ends should be set to 2 in the General UML Guidelines.
The Add-wizard should respect that number and make it possible to create 2 Connector Ends.
|MMA-542||General UML guidelines||
General UML Modeling Guidelines: Associations can contain other classifiers besides use-cases
| The "Association" meta class can invalidly contains "Class Item"
This is a necessary exemption until association classes are supported. Currently association classes are identified as associations by MMA, and association classes are allowed to have other nested elements
The location of a referenced element is not considered when matching meta-classes representing external elements
| An element must be in another model to be able to be matched with a meta-class representing an external-element
A fix of this bug may reveal new (unknown) problems in customer models.
All bugs applies to all environments, any exemption is indicated in the Component column:
|RSA||Only present when using IBM Rational Software Architect.|
|Papyrus||Only present when using Papyrus Modeling environment.|
|Windows||Only present when running on a Windows platform.|
|Linux||Only present when running on a Linux platform.|
|IOS||Only present when running on an Apple IOS platform.|
To use the hyperlinks in the tables, you must have authorized access to Adocus JIRA issue tracking repository.