Answers to: Use Axon.ivy Engine libraries in a plain Java process (Not Supported)

Answer by AxonIvyDeveloper

AxonIvyDeveloper — Mon, 05 Nov 2018 03:01:34 -0500

Ok I found already a part of the answer:

If provided jar is removed from the osgi environnent we can add it to the ear and to the ear classpath. I still dont know If old pmv dependencies are still going to work.

Do somebody know anything related to old pmv migration? Are the dependencies also persisted?

I believe that the dependencies of each ears are persisted with the PMV version in the Axon temp folder. So that when we migrate to a new Axon Ivy Version we don't have to provide 2 or 3 different versions of Hibernate, or JSF or some random lib that were removed.

Answer by AxonIvyDeveloper

AxonIvyDeveloper — Thu, 25 Oct 2018 05:18:27 -0400

Actually I found a new one, before the documentation or anything is updated I want to report again that some library are not in both available:

This time I found that javax.inject-1.jar is present in the Designer Axon.Ivy base libaries but not in the Engine!

I searched in the documentation and I cannot find any entries in the https://developer.axonivy.com/doc/7.0.latest/readme-engine for the text inject!

Last time sadly I saw the problem and needed to wait 3 weeks before that someone answered, so a lot of thing can change in 3 weeks but today the 25.10.2018 I really didn't found anything about the javax.inject library in the engine readme, but this is present in the designer.

Thanks for the help and cheers, Axon Ivy developer

Answer by Reguel Wermelinger

Reguel Wermelinger — Tue, 23 Oct 2018 06:14:46 -0400

We rely on a proper OSGi classpath. So we can avoid ClassLoading problems and dependency resolution conflicts (aka JAR-Hell). Trying to run normal Java-Code with our OSGi bundle JARs is not recommended or supported. So you should not use your own Main class or similar. But you can run any java code safely within our IvyProject environment.

If you face classloading issues in build process with maven you could share a flat classpath of the engine to provide build dependencies. But not to run an Java process on it. See https://axonivy.github.io/project-build-plugin/release/7.0/share-engine-core-classpath-mojo.html