BPEL Build and Project Dependencies

Question

Hi,
We are developing set of BPEL processes using jDeveloper 10.1.3.1
As part of this development, we want to develop set of utility classes which will be used in one or more of the BPEL processes using java embedding. Also these utility java classes make use of libraries like Oracle content services FDK etc.
For this we have created a project called BPELCommon and are writing the common java classes in this project and also created various project level library setting against this project. Then made the other BPEL project depend on this BPELCommon project using Project dependency settings.
However, when we try to build and deploy the BPEL processes using the automatically generated build.xml xml, it is failing to access and compile the classes and the project library files from the BPELCommon project.
Tried creating a pre-build.xml file which explicitly compiles the files from the BPELCommon/src folder into the BPELProcess1/output folder using libraries. It creates the classes under the BPELProcess1/output but still “bpelc” fails to access them and to bundle the project libraries into the BPEL Suitcase.
I believe this is pretty generic requirement since anyone developing more than one bpel process would always look for some code reusability.
Is there a way to change the build.xml to take care of project dependencies? ie to compile the java files from BPELCommon project and bundle the compiled classes along with the library jars while building the BPEL Suitcase?
regards - rutwik

Answer 1

One of the key goals doing SOA BPEL/ESB projects is creating an automated build system. Oracle SOA is not delivering this, but it gives you the tool do do so; like all the ANT stuff. So if you have your developed reusable, you must create your own build system. I wrote an article on this on my blog
http://orasoa.blogspot.com/2006/08/using-ant-in-bpel-environment.html
Marc