Before adding a custom Java service to a project, ensure that a Java service is the best way to provide the desired functionality. A straight Java service may not be the best solution if you expect to reuse the functionality in other projects.
One option is to package the core functionality up into a JAR file. This makes it easier to reuse the functionality provisioned by a set of classes. Subsequent projects will still need to use a Java service; however, they don't need to recompile another copy of the Java sources. Instead, the JAR file is added to the classpath and the Java service class uses the classes of the JAR just like any other JAR file import. This can be a good option if your organization produces JAR files as artifacts from other projects. Simply take the output targets from those builds and bring them into the WaveMaker projects. The downside to this approach is that any updates to the classes in the JAR file must be propagated to each project using the...