In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.
This chapter requires a local JDeveloper install with SOA extensions.
When you create a new "SOA Application" using JDeveloper's "New Gallery", a pom.xml for that composite is generated for you. In addition, a parent pom.xml containing the child projects is generated as well. The pom.xml file is the primary means of configuring a Maven project. The specific details of it can be found here.
BIG WARNING: JDeveloper defaults the revision to "1.0" whereas Maven expects the revision to "1.0-SNAPSHOT". To work seamlessly across both, you should change the "revision" in composite.xml:
<composite name="MyComposite" revision="1.0-SNAPSHOT" ...>
and the "composite.revision" in pom.xml:
When doing a release through Maven, it is important to remember that this version number is embedded in the composite.xml in addition to pom.xml.
For more information about building composites, please see Oracle documentation.
The accompanying video shows the process better than a thousand of my words.While Linux is used in the video series, all mvn and git commands are applicable to Windows. Any variations will be called out in the accompanying blog.