xoom-designer
compressed distribution file via curl
.zip
format, download it as follows:tar
format, download it as follows:VLINGO_XOOM_DESIGNER_HOME
indicating 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.xoom
shell script to run the XOOM Designer:xoom.bat
to execute the XOOM Designer software:pom.xml
already references the XOOM libraries needed to support the build and runtime execution of the microservice. The build is ready to run.xoom-turbo.properties
file 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, namelyxoom-turbo.properties
.my-xoom-microservice
, which has an initial version 0.1.0
. curl
or Postman to send HTTP request messages to the service according to your REST API design.pom.xml
already references and includes all of the XOOM library dependencies needed in order to build and run the microservice.jar
files from three primary public repositories GitHub, Sonatype, and Maven Central.SNAPSHOT
builds on Github. If you want to use the latest code you may reference it as artifactId-x.y.z-SNAPSHOT
. You must provide Github credentials to Maven in order to pull snapshots.pom.xml
file to reference the XOOM Turbo toolkit:jar
file. For example, xoom-turbo
references other libraries such as xoom-lattice
, xoom-http
, xoom-actors
, and others. In other words, you need only reference xoom-turbo
as a dependency and all others required will be resolved automatically.pom.xml
for the location of our snapshots.x.y.z
is 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.1.7.0
applies to xoom-turbo
then it also applies to xoom-lattice
and 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.md
for each open source artifact also references the current API-based Javadoc. For an example see the vlingo-actors README.md
.