4.0.0 org.simple4j WSOrchestrator 25.12.22.0 jar WSOrchestrator https://github.com/simple4j/WSOrchestrator MIT License http://www.opensource.org/licenses/mit-license.php Srinivas Janakiraman jsrinivas@simple4j.org Simple4j https://github.com/simple4j scm:git:https://github.com/simple4j/WSOrchestrator.git scm:git:https://github.com/simple4j/WSOrchestrator.git https://github.com/simple4j/WSOrchestrator WSOrchestrator-25.12.22.0 ossrh https://ossrh-staging-api.central.sonatype.com/content/repositories/snapshots ossrh https://ossrh-staging-api.central.sonatype.com/service/local/staging/deploy/maven2/ org.simple4j WSClient 25.06.30.0 org.springframework spring-context 6.1.13 org.slf4j slf4j-api 2.0.16 org.apache-extras.beanshell bsh 2.0b6 com.fasterxml.jackson.datatype jackson-datatype-jsr310 2.13.4 org.mvel mvel2 2.5.2.Final junit junit 4.13.2 test org.wiremock wiremock 3.9.1 test org.springframework spring-context-support 6.1.13 test ch.qos.logback logback-classic 1.5.8 runtime org.slf4j jcl-over-slf4j 2.0.16 runtime org.slf4j log4j-over-slf4j 2.0.16 runtime org.slf4j jul-to-slf4j 2.0.16 runtime org.freemarker freemarker 2.3.33 runtime release-profile org.apache.maven.plugins maven-source-plugin 2.2.1 attach-sources jar-no-fork org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar org.apache.maven.plugins maven-gpg-plugin 1.5 sign-artifacts verify sign --pinentry-mode loopback src/test/resources **/*.jks **/*.cer **/*.csr true src/test/resources **/*.jks **/*.cer **/*.csr false org.sonatype.plugins nexus-staging-maven-plugin 1.6.7 true ossrh https://ossrh-staging-api.central.sonatype.com true com.thoughtworks.xstream xstream 1.4.15 org.apache.maven.plugins maven-release-plugin 2.5.3 This is a simple orchestrator for Web Service API calls. It supports hierarchy of flows and steps with wiring of request response objects using templated variable replacement. Peer steps in a flow are executed in sequence and the peer flows are executed in parallel across multiple threads. A flow can have series of steps and sub-flows. They are executed in the natural ordering of their names. Based on natural ordering, if there are sequence of steps, followed by sequence of sub-flows, followed by another set of steps, then the first set of steps will be executed in sequence, then the sub-flows will be executed in parallel, then wait for all the sub-flows to finish and execute the second set of steps in sequence. 17 17