I use the following approach, but it is for ant, not for maven:
(it is actually not for ODE but for Intalio BPMS server community
edition but it possibly can be adapted for ODE)
The bpelc ant task is initialized by the following target:
<target name="init">
<taskdef file="bpmsTasks.properties">
<classpath>
<fileset dir="${intalio.bpms.server.home}/repository"
includes="**/*.jar" />
</classpath>
</taskdef>
</target>
bpmsTasks.properties file contain only one string:
bpelc=org.apache.ode.tools.bpelc.ant.BpelCTask
${intalio.bpms.server.home} variable points to the intalio server home
directory. In case of an ODE it will depend on an integration layer you
use (WEB-INF/lib for JBI integration or something like that)
The BPEL compiler is called with the following target:
<target name="compile" depends="init">
<bpelc targetdir="${cbp.build.dir}">
<bpel url="${path_to_bpel_file_1}" />
<bpel url="${path_to_bpel_file_2}" />
<!-- ... -->
<bpel url="${path_to_bpel_file_n}" />
</bpelc>
</target>
${cbp.build.dir} - is the output directory for compiled processes
WARNING!!! This is possibly unsupported way and the ODE internals may
change. I hope Intalio guys will clarify it.
wolfgang10 wrote:
Is it possible to incorporate the bpel compile in the maven build?
It would be nice to know any errors before the process is actually deployed
to the runtime.
Wolfgang
