Folks,

the API now gets its artifacts configured through the MC

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:bean-deployer:2.0 bean-deployer_2_0.xsd"
 xmlns="urn:jboss:bean-deployer:2.0">

 <!-- The process engine -->
 <bean name="jBPMProcessEngine" class="org.jbpm.integration.client.ProcessEngineImpl">
 <property name="processDefinitionManager"><inject bean="jBPMProcessDefinitionManager"/></property>
 <property name="processInstanceManager"><inject bean="jBPMProcessInstanceManager"/></property>
 <property name="executionManager"><inject bean="jBPMExecutionManager"/></property>
 </bean>

 <!-- The process definition manager -->
 <bean name="jBPMProcessDefinitionManager" class="org.jbpm.integration.client.ProcessDefinitionManagerImpl">
 <!--property name="processEngine"><inject bean="jBPMProcessEngine"/></property-->
 </bean>

 <!-- The process instance manager -->
 <bean name="jBPMProcessInstanceManager" class="org.jbpm.integration.client.ProcessInstanceManagerImpl">
 <!--property name="processEngine"><inject bean="jBPMProcessEngine"/></property-->
 </bean>

 <!-- The execution manager -->
 <bean name="jBPMExecutionManager" class="org.jbpm.integration.client.ExecutionManagerImpl">
 <!--property name="processEngine"><inject bean="jBPMProcessEngine"/></property-->
 </bean>

</deployment>

With this abstraction in place it should now be possible to implement the mapping for the JBPM4 code base

You can consume the API and the related tests from

http://snapshots.jboss.org/maven2/org/jboss/jbpm/

cheers