v15.1 – NO Native XMI transport for Controlled Packages

[Paolo F Cantoni]

We've started using the Native XML export a LOT!  It's so much faster than the more traditional XMI export (especially for large packages).

We use it particularly to move packages between repositories.  However, it's not available as an option on the Controlled Packages dialog.  Why not?

Is it possible to "jam" the selection via direct SQL injection?

Reported,
Paolo

[Eve]

The format to export appears to be in t_package.UMLVersion.

I have no idea if you'll get the result you're hoping for even if you do change it.

Of course although unsupported there is an API that allows you to run a sql update, you don't need to use SQL injection to get the job done.

[Paolo F Cantoni]

The format to export appears to be in t_package.UMLVersion.

I have no idea if you'll get the result you're hoping for even if you do change it.

Of course, although unsupported there is an API that allows you to run a SQL update, you don't need to use SQL injection to get the job done.

Yes, I'd spotted that.  But the values didn't make sense.  Today, after some more testing, they do.  The problem is (as I indicated) that since there is no selection for (o) Native in the Controlled Package dialog, I don't know what value to "jam" in.  The Export-XML Export Type values are transient and not persisted to the DB, so I can't tell what they are (and, this being EA, quite probably NOT consistent with the Controlled Package values).

What would the value be?  Based on the current values, "Enterprise Architect Native"?

The reference to "SQL injection" was merely to imply NOT going through the UI.

Paolo

[Eve]

If you put anything but the values allowed by the UI EA will default back to a standard XMI version of XMI 1.1.

Probably good behavior even though it's not what you would like to hear.

[Paolo F Cantoni]

If you put anything but the values allowed by the UI EA will default back to a standard XMI version of XMI 1.1.

Probably good behavior even though it's not what you would like to hear.

Yes, not what I wanted, but not unexpected.

So I'll have to wait until the feature is implemented (if ever).

On a related matter, when we import using the direct import (rather than Controlled Package)  we don't specify the nature of the XMI, and EA adapts (as far as I can see).
Do you know if the Controlled Package import can adapt in the same way?  If so, then maybe I can go half-way since the import is the problem (see either post).

Paolo

[Eve]

Give it a try and see what happens.

Your other option would be to script the native export.