Hello,
For those of us using Java in general, we have to start moving to Java 11, and all Java providers, commercial or open source, stop support for 32-bit jre and jdk altogether.
This means that any automation we have today to interact with our EA models will just stop working.
It is very costly or even impossible to:
- port existing Java application talking with EA to some other programming language, and/or,
- train developers to learn another programming language (e.g., C#), and/or,
- change the enterprise server-side infrastructure to remove Java from the picture,
the options some have been proposing on other related threads

Does Sparx have plans for:
1) providing 64-bit Java API (eaapi.jar, and probably accompanying SSJavaCOM.dll)?
2) providing faster
COM-independent implementation, now that there is native EA XML export?
In relation to 2): Many years ago, being desperate with the bad EA Java API performance, I have indeed developed an alternative 'builderFromEa' implementation
for the basic UML model content that my open source application (
http://www.tanjakostic.org/jcleancim/) needs. It took me a few week-ends back then to:
- refactor my original code that was using exclusively EA Java API iterative model walk-through, and,
- provide an alternate (now default) builder that works with SQL query results returned as XML (as recommended by Geert).
Indeed, the only times I must use EA Java API today is when I need to export diagrams and/or XMI. These operations are, again, notoriously slow (qwerty and Geert explained why in a previous thread) and this would be also something for Sparx to consider improving.
Could anybody from Sparx comment on this? It is really getting urgent to support 64-bit jre/jdk at least for read-only access.
Thanks,
Tanja