The Integration blog covers the latest in product updates, best practices, customer stories, and more.

  • September 30, 2015

SOACS plus DevCS - Chapter 06

In this series of posts and videos, we will explore creating and deploying a SOA composite using Oracle Developer Cloud Service.

< Previous Chapter | Next Chapter >

Chapter 06 - Creating Composites with JDeveloper and Maven

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.

Helpful links:

Join the discussion

Comments ( 4 )
  • Oracle Training Company Wednesday, September 30, 2015

    Educative, enjoyable & fun video. The easy to learn methodology.

  • guest Wednesday, July 13, 2016

    When i create a project i am not getting the POM by default, can you please let me know what i am doing wrong.

  • Vikram Friday, July 15, 2016

    I am unable to get the POM file auto generated when i create the application. What should i be doing.

  • guest Friday, July 15, 2016

    Hello Vikram. I used base 12.1.3 JDeveloper for the demo. I tried it with other JDevelopers (12.2.1 at the time) and the pom.xml was not generated. This might have been fixed with patches since I last tested in 2015

    Either way, I recommend using mvn plugin directly to create the structure and importing the project into JDeveloper afterwards.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.