Author Topic: EAP vs EAPX  (Read 2657 times)

Modesto Vega

  • EA User
  • **
  • Posts: 376
  • Karma: +7/-4
    • View Profile
EAP vs EAPX
« on: March 12, 2019, 08:32:04 pm »
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

  • EA Guru
  • *****
  • Posts: 9547
  • Karma: +275/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EAP vs EAPX
« Reply #1 on: March 12, 2019, 08:50:45 pm »
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

  • EA User
  • **
  • Posts: 376
  • Karma: +7/-4
    • View Profile
Re: EAP vs EAPX
« Reply #2 on: March 13, 2019, 04:37:09 am »
Thanks Geert

Stephan Amsbary

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: EAP vs EAPX
« Reply #3 on: June 11, 2019, 01:17:06 am »
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

  • EA User
  • **
  • Posts: 869
  • Karma: +67/-5
  • Its the results that count
    • View Profile
Re: EAP vs EAPX
« Reply #4 on: June 11, 2019, 05:55:23 am »
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.
Happy to help
:)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9547
  • Karma: +275/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EAP vs EAPX
« Reply #5 on: June 11, 2019, 01:33:07 pm »
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

  • EA Novice
  • *
  • Posts: 6
  • Karma: +0/-0
    • View Profile
Re: EAP vs EAPX
« Reply #6 on: June 12, 2019, 11:50:48 pm »
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

  • EA Guru
  • *****
  • Posts: 9547
  • Karma: +275/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: EAP vs EAPX
« Reply #7 on: June 13, 2019, 01:36:42 am »
You'll have to do a model transfer from a .eap file to a .eapx file.

Geert

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 6847
  • Karma: +66/-7
    • View Profile
Re: EAP vs EAPX
« Reply #8 on: June 13, 2019, 09:04:29 am »
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.
Eve

support@sparxsystems.com