xoom-designercompressed distribution file via
zipformat, download it as follows:
tarformat, download it as follows:
VLINGO_XOOM_DESIGNER_HOMEindicating the absolute path of the uncompressed folder; that is, the root of the installation folder, not the parent directory where it was decompressed. Using a *nix shell, such as
bash, do this:
.bash_profile, for example. This makes the XOOM Designer ready for use after logout followed by login.
xoomshell script to run the XOOM Designer:
xoom.batto execute the XOOM Designer software:
pom.xmlalready references the XOOM libraries needed to support the build and runtime execution of the microservice. The build is ready to run.
xoom-turbo.propertiesfile to support the proper database connections. Defaults are generated for databases such as Postgres and MariaDB, and others, but these might not match your local environment. Additionally, if your microservice is event driven and receives incoming event messages or produces outgoing event messages, specify the proper connection configurations for your message broker/bus in the same properties file, namely
my-xoom-microservice, which has an initial version
curlor Postman to send HTTP request messages to the service according to your REST API design.
pom.xmlalready references and includes all of the XOOM library dependencies needed in order to build and run the microservice.
jarfiles from three primary public repositories GitHub, Sonatype, and Maven Central.
pom.xmlfile to reference the XOOM Turbo toolkit:
jarfile. For example,
xoom-turboreferences other libraries such as
xoom-actors, and others. In other words, you need only reference
xoom-turboas a dependency and all others required will be resolved automatically.
pom.xmlfor the location of our snapshots.
x.y.zis representative placeholder of the semantic version number of the given artifact. Both stable releases and daily snapshot builds are provided on Sonatype, and release artifacts are hosted by Maven Central. Generally the tip revision of each JAR file listed in the repository is the one that will work together with all others as a whole platform.
xoom-turbothen it also applies to
xoom-latticeand the remaining platform components. The following is an example that uses platform version
1.7.0, but the version should be adjusted to your specific dependencies.
README.mdfor each open source artifact also references the current API-based Javadoc. For an example see the