By Juergenkress-Oracle on Feb 17, 2015
I recently started to build a small project in JDeveloper 12c to learn how to make use of Custom Activities in an Adaptive Case Management project. The results of this project will be posted in my next blog. When I started the project, I wanted to do it the Maven way (since JDeveloper 12c has built-in Maven support).
Being able to deploy a case as a Maven artefact requires a little initial setup. The bulk of the initial setup can also be found in a blogpost referenced in this Whiteblog from colleague Dirk Janssen. I decided that the complete setup justified a blogpost on its own. So in this post I’ll demonstrate how to deploy the (skeleton of the) case application via Maven. In the next blogpost I’ll enhance the case application with custom case activities.
Creating the application
First things first, let’s create a new BPM application CustomActivitiesDemo and add a project called CaseWithCustomActivities to the application. Choose Composite With Case Management as the project type. After you’ve created the project, you get 2 POM files for free. One aggregate POM file for the application and the POM file for the case project. Per default the groupId equals the application name (CustomActivitiesDemo). I don’t like that, so let’s change the groupId into something more structural, like nl.whitehorses.acm.
If you take a look at the generated project POM file you’ll see that it has a reference to a parent pom com.oracle.soa:sar-common.
As you can see in the picture below, the curly lines indicate that the
parent POM can’t be found right now. So let’s fix that, by adding the
necessary artefacts to our Maven repository. Read the complete article here.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.