...
list - attribute of the complex object, if = "true", complex object is translated to array list, valid both in request and response
Attributes:
...
Getting started
In order to get started with SOAP workflow framework you will have to include the Maven artifact in your pom.xml file as a runtime dependency.
| Code Block | ||
|---|---|---|
| ||
<dependency>
<groupId>com.cdrator.integration.soap</groupId>
<artifactId>rator-soap-workflow</artifactId>
<version>2.4</version>
<scope>runtime</scope>
</dependency> |
If you are adding the SOAP workflow functionality to a existing customer project, then it is the best to implement this as a project module. E.g.: SIMYO/modules/workflowSoap/pom.xml. Note that usually the artifact dependency is specified in the parent pom.xml file with the version specified (e.g.: SIMYO/pom.xml):
| Code Block | ||
|---|---|---|
| ||
<dependency>
<groupId>com.cdrator.integration.soap</groupId>
<artifactId>rator-soap-workflow</artifactId>
<version>2.4</version>
</dependency> |
and in the module pom.xml file with the scope (e.g.: SIMYO/modules/workflowSoap/pom.xml):
| Code Block | ||
|---|---|---|
| ||
<dependency>
<groupId>com.cdrator.integration.soap</groupId>
<artifactId>rator-soap-workflow</artifactId>
<scope>runtime</scope>
</dependency> |
Also, don't forget to include the following dependency to build the deployable WEB application WAR file:
| Code Block | ||
|---|---|---|
| ||
<dependency>
<groupId>com.cdrator.integration.soap</groupId>
<artifactId>rator-soap-workflow</artifactId>
<classifier>webapp</classifier>
<type>war</type>
<scope>runtime</scope>
</dependency> |
In addition to that, configure the build process, Maven renamer and Maven WAR plugins. The example build section configuration might look like this:
| Code Block | ||
|---|---|---|
| ||
<build>
<finalName>simyo-workflow-soap</finalName>
<plugins>
<plugin>
<groupId>com.cdrator.maven.plugins</groupId>
<artifactId>rator-maven-renamer-plugin</artifactId>
</plugin>
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<outputDirectory>${project.parent.build.directory}</outputDirectory>
</configuration>
</plugin>
</plugins>
</build> |
Last thing to mention about this artifact is that starting from version 2.0 it uses JAX-WS for exposing endpoint.