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 ... 389 390 [391] 392 393 ... 416
Frank is right that modifying the XML files would be the quickest/easiest way to do it.  Tip. You can see what files correspond to what packages by looking at ModelPatterns\models.xml.   You can also add new packages and groups this way.

For something that you don't need to worry about during an upgrade you should look into MDG technologies.  You'll have to directly edit the MTS file, but the instructions for this are at

Those fields will be accessible when using the attributes dialog for datamodeling elements (such as table).

Have a look at predefined tagged value types and then:

Create an MDG Technology that bundles your UML Profile and your tagged value type definitions into a single file. Then when you import the technology your target model is guaranteed to have the tagged value types.

You can get more than a text filter, you can get a date field complete with a date selector.

Automation Interface, Add-Ins and Tools / Re: Security Problems
« on: June 12, 2008, 02:12:03 pm »
David is right about one thing.

You can't go wrong with a feature request.  The function has the extra options there so that it can be extended to take more options without breaking existing callers.

Automation Interface, Add-Ins and Tools / Re: Security Problems
« on: June 12, 2008, 08:28:44 am »
There isn't (currently) any way for for the automation function to override this option.

  • You can either ensure that no-one turns the option on.


  • You can write into your automation client something that clears the code property for all methods.


  • You can write a sql call do do the same thing.

EA doesn't support tagged values on diagrams.  I remember a discussion some time ago where someone was saying that we should.

Maybe it would be nice, but they aren't UML elements, so I would categorize it as a feature request rather than issue of any sort.

Automation Interface, Add-Ins and Tools / Re: SVN and XMI version
« on: June 06, 2008, 08:14:24 am »
No.  The only format currently supported for version control is XMI 1.1 for UML 1.3.

If you're concerned about loss of data because of the format, it's fine.  EA won't lose the information.

If you're wanting to use the XMI with other tools that only import XMI 2.1, you'll have to export the packages seperately.

Drop the Action metaclass.
Open the attributes dialog.
Select the kind attribute.
Click on the ellipsis (...) button to select CallOperation.

I tried to access EA via java, too. In your case i do not get this exception, but the collection "packs" is null.
I am not able to access any model or something else.

Does anybody have a solution.
Upgrade to the latest build.  There was a problem with the Java API of early 7.1 builds.

That's an issue where somewhere in the wrapper it's not handling unicode strings properly.  We'll correct that, but in the mean time I suggest that the error would be "Invalid Argument".  How to resolve that would depend on what arguments you're passing and to what collection.

The classes and methods are identical in the eaapi.jar to what is described.

You can customize the main menu using Tools | Customize.  The context menus aren't customizable though.

I've split this into a topic of its own because it isn't really about the same thing as the original post.

If you select the '(diagrams template)' template, then you should get what you want.

If you want more control than that, create a new template based on (diagrams template)'.

Automation Interface, Add-Ins and Tools / Re: XMI validation
« on: May 29, 2008, 08:16:26 am »
Well, it's not as if the document is unstructured.

The metamodel used for the XMI controls what can go where.

So, if you want to validate EA's XMI 2.1 output have a look at the XMI 2.1 specification and the UML 2.1 specification.

Automation Interface, Add-Ins and Tools / Re: XMI validation
« on: May 28, 2008, 07:43:49 am »
Unfortunately, that is the XMI 2.1 schema.  I'm not aware of anything more detailed (official or not).

Pages: 1 ... 389 390 [391] 392 393 ... 416