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 ... 392 393 [394] 395 396 ... 413
Automation Interface, Add-Ins and Tools / Re: Code Generation
« on: October 21, 2007, 01:15:56 pm »
You're after linkParentName or linkParentQualName and these can be found at or in any existing template.

Automation Interface, Add-Ins and Tools / Re: SqlQuery SQL Syntax
« on: October 16, 2007, 06:07:16 pm »
I would treat it as though you are making a direct query to the database being used.

Automation Interface, Add-Ins and Tools / Re: Tranformation - "copy"
« on: October 15, 2007, 01:02:26 pm »
Internal requirements are currently not handled by the transformations.   (Internal test cases, files, constraints are also not handled)

Make sure you've added the attribute to the metaclass, not the stereotype.  Then it won't create automatically unless you have also set _makeComposite as true.

I don't think you can.  It would be more appropriate to use a pattern to do this.

Try checking the return value of OpenFile.  I suspect that it failed.

Try passing in an absolute file path.

Well, actually I'd like to create a brand new .eap via automation interface without any prepared existing .eap files somewhere.
I do not want to be dependent on some storage with an empty .eap file.

Even EA can't do this.  It relies on EABase.eap being in the same directory as the executable.

You can't edit tagged values directly on non-shape scripted elements, and I don't think there is a way to do it on shape scripted elements.

Automation Interface, Add-Ins and Tools / Re: XMI export to Eclipse/EMF
« on: August 16, 2007, 02:35:25 pm »
Even if EA was to generate 100% of the data into the main portion of the XMI document instead of the extension my point still remains.  They are still incompatible versions of XMI.  However, I believe we have plans for an option to export to an EMF compatible metamodel.

PS. The example you have given, is an example of something that EA allows that isn't supported by the UML metamodel.  (An attribute type that isn't included in the current model)

Automation Interface, Add-Ins and Tools / Re: XMI export to Eclipse/EMF
« on: August 15, 2007, 04:41:53 pm »
I haven't tried it myself, but I think the issue is that Eclipse EMF isn't expecting an EMF XMI file instead of a UML XMI file.  EA currently doesn't support exporting to this format.

So (if I remember correctly) it's not an issue with compliance to the XMI spec for either tool.  It's that EMF doesn't use UML as such.

Automation Interface, Add-Ins and Tools / Re: Slow collection access
« on: September 18, 2007, 01:09:35 pm »
Have you set Repository.EnableCache to true?

You can't currently get information about attributes/columns/operations of the target(or opposite end from current) object of a connector without using an addin and EXEC_ADD_IN.

That particular macro came from with the line

connectorDestElem*   For any class substitution macro that is supported, get the same information about the element at the target end of the connector.  Also try searching for code template syntax.

Create this as a custom template.

Template Connector__DestName
Code: [Select]
Then call a list that looks like this.

Code: [Select]
%list="Connector__DestName" @separator="\n" @indent="" connectorStereotype=="family"%

No, the XSD schema dialogs are part of EA, not an addin.  But you can achieve a similar effect as I described.

Pages: 1 ... 392 393 [394] 395 396 ... 413