no magic catia logo

Integrations

The problem is outdated Xerces library, used by MagicDraw. Please remove this library (it is not necessary, because java 1.5/1.6 already has XML parsing in the standard install).

There is also a workaround. Please specify the-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp. SAXParserFactoryImpl parameter for the Java when running the workflow. This will force the script to use Java's default implementation instead of one brought in by MagicDraw.

You should modify the idea.properties file in the IntelliJ: idea.popup.weight property set to medium. After editing it should look like that: idea.popup.weight=medium

Since MagicDraw version 12.5, Eclipse and MagicDraw works together on Mac OS X with JVM 1.6.0.

Since MagicDraw 10.5 version, integration with Eclipse supports Java 5.0 code engineering.

Since MagicDraw 15.0 version, integration with NetBeans and JBuilder (works only up to MaigcDraw v17.0.1) supports Java 5.0 code engineering also.

Yes, MagicDraw Standard edition, as well as Professional integrates with Eclipse, WSAD, JBuilder (works only up to MaigcDraw v17.0.1), Sun One Studio, and NetBeans without any problems. The difference is that the Standard edition itself has no code engineering functionality but this does not have any impact to the integration.

Yes. We currently have integrations with Eclipse 3.1 or later (JDT or Java IDE), JBuilder 8.0, 9.0, X, 2005, 2006, 2007 (works only to MagicDraw v17.0.1), 2008, IBM RAD 7.0, IBM RAD 7.5, BEA WebLogic Workshop v9.2, v10.1, v10.2, Netbeans 6.0 or later, Sun Java Studio 8, Sun ONE Studio 5 (works only up to MagicDraw 10.5 version), IntelliJ IDEA 4.5 or later.

MagicDraw integrates with IntelliJ IDEA 4.X or later

The solution is to close and reopen Diagram View or Browser tabs in all Eclipse perspectives.

Please, try to add such line -DdefaultFont=true in eclipse.ini file after vmargs.

The lines should look like:

-vmargs

-DdefaultFont=true

After unintegration, old directory is still remembered by Eclipse. The solution is to unintegrate Eclipse from MagicDraw, then start Eclipse, close it, and only then integrate with new MagicDraw version and launch again.

Some JVMs put restrictions on the total amount of memory available on the heap. If you are getting OutOfMemoryErrors while running Eclipse, the VM can be told to let the heap grow to a larger amount by passing the -vmargs command to the Eclipse launcher. For example, the following command would run Eclipse with a heap size of 512MB:

eclipse [normal arguments] -vmargs -Xmx512M [more VM args]

Some JVMs have restrictions on permanent generation memory, which can be exceeded in integration. In order to increase permanent generation memory size, you need to specify additionally -XX:MaxPermSize (use it for Sun JVM). For example, the following command would run Eclipse with a permanent generation memory size of 128MB:

eclipse [normal arguments] -vmargs -XX:MaxPermSize=128M [more VM args]

Sometimes when starting MagicDraw from Eclipse, MagicDraw is not started. This problem can appear after MagicDraw version update. The solution is to launch Eclipse with the -clean parameter first time when this problem appears:

eclipse -clean

If you have specified property "-Dsun.java2d.d3d=false" in "eclipse.ini", try to remove it or set the "true" value.

MagicDraw 17.0 SP2 and earlier is not compatible with Eclipse 3.7.

We suggest you to integrate MagicDraw 17.0 SP2 with Eclipse 3.6.

uml2ecore transformation of openArchitectureWare framework does not work on Linux, Mac OS

Symptom: you get the following error when doing uml2ecore transformation:

797 INFO CompositeComponent - Generator.contraintsEtc: generating 'org::openarchitectureware::util::uml2ecore::templates::files::root FOR ecoreModel' => directory 'meta/' 7823 ERROR WorkflowRunner - org/openarchitectureware/util/uml2ecore/templates/files.xpt: unexpected char: 0xFFFD (Note, that char may be different, e.g. on Mac, unexpected char: 0xB4 is encountered)

Cause: uml2ecore transformation contains a bug, which precludes it from working on systems, where default file encoding is non standard. For example on Ubuntu v7.04 (Feisty Fawn) default encoding is UTF-8; Mac OS X, MacRoman encoding is used bu default. This causes transformation to fail, because files.xpt template file in the transformation plugin is encoded in ISO-8859-1.

This bug is not a bug in MagicDraw, but a bug in openArchitectureWare. This bug is acknowledged and tracked in oAW bug list: https://bugs.eclipse.org/bugs/show_bug.cgi?id=177956 This bug is present in oAW v4.1.2. Currently we do not know, when this issue will be fixed.

Workaround:

1) locate the uml2ecore plugin jar file. This file is usualy /plugins/org.openarchitectureware.util.uml2ecore_4.1.2.v20070314.jar (note that version numbers/dates may be slightly different in your install). Backup this file somewhere, we will be editing it.

2) inside this jar archive, locate uml2ecoreWorkflow.oaw file, open it in editor and scroll to the bottom.

3) locate the oaw.xpand2.Generator invocation component (id="Generator.contraintsEtc"), and add additional tag inside. Here is the final result you should get:

.....

4) update jar archive with this new version of uml2ecoreWorkflow.oaw file

5) restart Eclipse.

uml2 ecore transformation should now run cleanly.

For more information or a quote
please contact
sales@nomagic.com
or call +1-214-291-9100.