Messages

1

General Board / Re: Association end stereotype with tagged values

« on: October 05, 2023, 02:15:42 am »

Still a problem in version 15.2. I make a nice UML-profile with mandatory/optional stereotypes applying to the attribute Metaclass and associationEnd Metaclass, but when importing the profile this works perfectly for the attributes bit not for the associationends (aka rolenames). Which is a pity if you have a lot of those. Adding a stereotype by means of the New button works, but then what's the use of all the UML-profile functionality?

2

Bugs and Issues / Re: caret symbol for inherited members?

« on: March 27, 2019, 08:20:40 pm »

I sent a mail to [email protected]. I have to ask our administrator here for the login and password for a priority bug report.

3

Bugs and Issues / Re: caret symbol for inherited members?

« on: March 27, 2019, 07:54:40 pm »

Illustration of this notation in MagicDraw here: https://drive.google.com/open?id=1nY_PGwSWvh7geJsuCqAPXCNbCdUoJB_U. The version I installed is 14.1.1429 which seems to be the latest right now.

4

Bugs and Issues / caret symbol for inherited members?

« on: March 27, 2019, 05:59:40 am »

UML 2.5 prescribes to show inherited attributes with a caret (^) symbol prefix. EA14 says it conforms to that, on https://sparxsystems.com/products/ea/14/index.html we read the following: "Inherited properties will now display with the caret (^) symbol before the name". I searched frantically in every option corner to activate that notation but to no avail, it's still the old notation with the name of the superclass before the attribute name. (I could attach an image of a model made with Magicdraw to illustrate this notation but the "insert image" function does not seem to work in my browser.) Thanks for helping me out here.   

5

Bugs and Issues / Re: Profile only partially imported

« on: September 18, 2018, 11:46:31 pm »

Which brings me to another problem now: tell me if you want a seperate post for it. The topic is: if a stereotype in a profile package has an abstract superclass, this abstract superclass logically does not show in the profile. Only problem: when loading the profile EA goes searching for the missing superclass and if it finds a match somewhere else in a built-in profile your stereotype gets the appearance of that stereotype. Example: I have a stereotype owlClass which in turn has an abstract stereotype Entity as its superclass. When saving the package as a profile the abstract stereotypes are excluded but with owlClass the superclass Entity is mentioned as basestereotype in the xml. After loading the profile and using the stereotype owlClass it has 2 stereotypes: owlClass but also Entity (from some built-in profile) and it takes on the appearance of the latter (which in this case is appearently a Business Class icon = a circle on a line) in stead of the class icon of owlClass. What to do about this?

6

Bugs and Issues / Re: Profile only partially imported

« on: September 18, 2018, 07:26:29 pm »

Thanks for your answer. That will indeed be the problem, a missing exension connector to the metaclass Class. Maybe merging the OWLprofile and the RDFprofile will provide a solution, for some reason the RDFS and OWL elements are provided by OMG in seperate packages which are not standalone. I also figured out that abstract classes do not show up in the profile, but that's logical: an abstract metamodel class should not be instantiated.
Concerning the OMD in EA: it only implements a very small subset of the OMG's Ontology Definition Metamodel, so I cannot use it to model in RDFS/OWL effectively. 

7

Bugs and Issues / Profile only partially imported

« on: September 18, 2018, 08:01:08 am »

There is a package from OMG with a OWL Profile, see https://www.omg.org/spec/ODM/About-ODM/. Importing the package https://www.omg.org/spec/ODM/20131101/OWLProfile.xmi and then saving it as a profile OWLProfile.xml works fine. I can then import the file as a profile, but sadly a lot of elements (eg owlClass) are missing from it. Can someone explain? Is there a limit on the number of elements per profile? Or is there another problem with the profile? Thank you for your help.

8

Automation Interface, Add-Ins and Tools / Re: Help with deploying add-ins

« on: April 04, 2018, 12:44:49 am »

I got it working. That is: the addin now loads in EA at startup and the Hello World example from Geert works fine. I followed several hints in your responses so now I do not know exactly what the error was . I will start over again from scratch and verify and document. But for now: thank you all for your expertise.

9

Automation Interface, Add-Ins and Tools / Help with deploying add-ins

« on: March 31, 2018, 12:51:00 am »

After two days of trying I am unable to succesfully deploy my add-in. On starting EA I get the Missing (0x800401F3) error. I try to deploy the demo addin from Geert Bellekens (see https://bellekens.com/2011/01/29/tutorial-create-your-first-c-enterprise-architect-addin-in-10-minutes/). I know that there is a problem with the registration of the dll altough I succeeded to register the dll with regasm. I tried the 32bit build, the 64bit build, I checked the correct COM interop options, I tried several versions of regasm to adapt to my target .NET framework, I tried the EAinstallerinspector (which confirms that that there is a problem with the registration of the dll altough the registration with regasm seems to work: it says Types Succesfully Registered). Is there any systematic way to verify step by step what is wrong or do I really have to quit the addin path. I really need some extra functionality in the transformation templates to transform my class diagram to generate an xsd. Seems that I am not the only one with the problem but I tried almost all suggestions (apart from re-installing .NET and other desperate measures). Thanks.