Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Simon M

Pages: 1 ... 390 391 [392] 393 394 ... 413
The above paradigm always works out in EA, because to be owned of an element, something must be owned by the same package as the element. I suspect - without proof, but I'd not care to test this on an important project - that if you built a project and got the PackageID of parent and child elements out of sync you would come to grief somewhere down the line.
It won't show up as you expect in the project browser.  However, it's a problem that can be fixed by the integrity checker.

Automation Interface, Add-Ins and Tools / Re: problem with form captio
« on: March 17, 2008, 08:31:59 am »
I suspect that this is relating to your application not correctly handling wide characters.

The original post would have been around the time that EA switched from separate unicode/non-unicode builds to unicode only.

Sparx has confirmed that the MDG event call is the way to go from EA 7.0 onwards.

That or a file. See

Beta 2 of 7.1 (build 826) should have corrected setting the IsChangeable property, including documenting the accepted values in the help file.

From memory I was working briefly on something similar to this.  I had to stereotype the instance.  (Shape scripts only apply based on a stereotype)

Automation Interface, Add-Ins and Tools / Re: Object Model : java help
« on: March 07, 2008, 03:58:21 pm »
I don't know about the destroy function, but I'm pretty sure it's not part of the EA automation interface.  (General java object function maybe?)

To remove a package you need to call RemoveAt() from the parent package Packages collection.

I could be wrong, but if the typecast is incorrect then the code won't even get to EA, and it won't be EA produced the access violation.

Automation Interface, Add-Ins and Tools / Re: Create Addin with java
« on: March 05, 2008, 08:17:27 am »
The Java API only includes the ability for Java to call EA.  The ability to write addins isn't included.  This has always been a limitation of the Java API.  Although I believe a COM wrapper for Java should be technically feasible, I haven't had the chance to prove this yet.

What Sparx has done is used a third-party middleware product to bridge between Java and COM.
Sorry, but this is misinformation.  The truth is that the middleware between Java and our COM interface is generated by EA.


You're right, this is wrong and should be corrected for our next build.

You need to create a custom template.  Select the type 'Parameter' and give a name such as 'Name'.

Edit that template to just give the parameter name.

Code: [Select]
%opName%The list in the calling template would then use the custom template you chose.  (Note. Two underscores)

Code: [Select]
$attr=%list="Parameter__Name" @separator=", " @indent="  "%

First question:

Reverse engineering does not create any links from this, and only creates associations, never aggregations or compositions.

Second question:
In the code generation dialog (for a single class) there is two fields for the imports needed. If you put the extra using statement in there EA will generate it out. (When generating the entire file)

Automation Interface, Add-Ins and Tools / Re: EA 7.1 RichText Editor
« on: February 28, 2008, 08:41:30 am »
The control itself isn't available, but the automation interface does provide two functions for doing the conversion for you.

See for a description of GetFieldFromFormat and GetFormatFromField.

Basically if you have an editor that produces rtf or html output you can convert that to a format suitable to be saved in an EA notes field using Repository.GetFieldFromFormat().

I hope that helps.

Thanks David.  I meant "set" as per the original question and have corrected my above post to reflect this.

EA never uses the language of a package, but that doesn't mean that it shouldn't allow a transformation to set a language. I'd recommend sending in a bug report to sparx systems.

What I see there, are some issues which are matters of personal style.  Others are not errors of the existing templates but that the templates are expecting you to do something that you arne't.

  • There is no recognition of the UML associations; hence attributes for these associations are not generated in the IDL. - There certainly should be, but some options will effect where these are used and not all types generated make use of attributes.  (I noticed that you modified the LinkedAttribute template.  This is for attributes created from associations)
  • Syntax error in the IDL code generated for an operation that raises an exception. (The Exception name is not enclosed in brackets) - EA is expecting the list of possible exceptions surrounded by brackets as this is how it is reverse engineered.
  • Incorrect code generated for a CORBA union; the keyword case is omitted in the generated code. - Again, the tagged value is expected to include the case keyword, as is done by reverse engineering.
  • Each value in a CORBA enumeration is listed on a separate line not an error, but an unconventional arrangement of code; - As I said, style issue only.  Exactly why templates are customisable.
For anything else, I'd recommend contacting sparx support directly.

As for the 'Generate CORBA Elements', you can easily write a transformation equivalent to this command and much better.  The addin was developed before transformations were available in EA.

Pages: 1 ... 390 391 [392] 393 394 ... 413