Hi Vineeth, jbpm-bpel is definitely compatible with jbpm applications, because it is an integral part of the product :-) Here are some answers to your questions: 1) Short answer: no. While BPEL and jPDL build on a common graph object model, they are very different languages. You cannot just bring, say, the receive activity from BPEL without bringing partner links, correlation sets, properties and other supporting BPEL concepts. You'd end up with an unelegant mix of Java and web services concepts. 2) Yes! BPEL-196 addressed deployment of BPEL and jPDL processes to the same installation (server and database combination). By installing the jbpm-bpel service archive as described in the user guide you can enact both jPDL and BPEL processes. You can even deploy the jBPM web console (jbpm.war) and monitor both kinds of processes using it. Unfortunately, the process instance inspection page is broken for BPEL processes, but this will be fixed in jBPM 3.2. 3) Yes. BPEL processes expose a web service interface that you can invoke from a jPDL process with the standard JAX-RPC client APIs. Do not try to use the subprocess node, tough. BPEL processes should only be created by invoking a web service operation. 4) It requires JMS and J2EE 1.4 web services. You could do this by deploying messaging and web services to tomcat on top of the microcontainer. And no, we haven't tried this before because JBoss AS already offers web services, JMS and much more. But hey, if you want to try, we will gladly help you :-) Best, View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976857#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...