EAP vs EAPX

[Modesto Vega]

With v14, Sparx has changed the extension of stand alone projects from EAP to EAPX. Does this means that v13 cannot read any stand alone projects created with version v14? How do I exchange stand alone projects between v14 and v13?

Does anybody have the technical details behind this change?

[Geert Bellekens]

There is no technical change, just a change in file extensions.

In pre v14 you could save .eap files with two formats: Jet 3.5 (default) and Jet 4
Now in v14 they have made the difference clear by using a different extension. (.eap for Jet 3.5, .eapx for Jet 4)
The default has now also changed from Jet 3.5 to Jet 4

You can still open .eapx file with EA v13. If you like you can rename the extension to .eap for more convenient access in v13.

Geert

[Modesto Vega]

Thanks Geert

[Stephan Amsbary]

Hi Geert, I upgraded from v13.5 to v14.1 because I could open a fellow employees eapx BD. I upgraded to v14.1... yesterday and while I can access their EAPX DB, new projects didn't allow my the full range of connectors eg: I can't connect an Event to a Process with a trigger, my "best" option is flow. I reported this to SPARX, and am right now really frustrated, and looking for my v13.5 install file.

Help

[Sunshine]

There is no technical change, just a change in file extensions.
...

Not quite true as Jet 4 with the eapx files allow unicode character encoding.

[Geert Bellekens]

There is no technical change, just a change in file extensions.
...

Not quite true as Jet 4 with the eapx files allow unicode character encoding.

Previously you could use Jet 4 files as well. You had to turn on the setting to use Jet 4, and start from the Jet4 base model.
Those files had the same .eap extension as the Jet 3.5 files.

Geet

[Stephan Amsbary]

Thank you Sunshine and Geert for your answers... That generates a new wrinkle to my question: I can't find this in the EA manual, how do I convert an existing EAP file to EAPx?... Does that "automatically fix the connector issue I'm having or do I need to recreate the Behavior elements to gain the correct connector options?

Thank you in advance for your time and consideration.

Regards, Stephan Amsbary

[Geert Bellekens]

You'll have to do a model transfer from a .eap file to a .eapx file.

Geert

[Eve]

Does that "automatically fix the connector issue I'm having or do I need to recreate the Behavior elements to gain the correct connector options?

If you mean that some ArchiMate connectors aren't being offered, migrating to .eapx won't help that.

[rchalie]

You'll have to do a model transfer from a .eap file to a .eapx file.

Geert

Would that be exporting to XMI, creating a new project (in 15.2) and the importing the XMI again?

[qwerty]

I would think that the model transfer is much quicker and actually has the purpose to migrate from one DB to another. XMI should work too, but much slower.

q.