I am sure that some exciting things will happen in the near future indeed. As you may know, jBPM was build from the beginning with multi language support in mind. Supporting XPDL seems a logical step, isn't it?
As for the JWT, it is also a logical step to cooperate with this project as it is aimed to do on the tooling side what jBPM is doing on the runtime side: provide support for multiple languages.
Thanks for the response.
My company is evaulting jBPM and we love its framework, but we'd like to use it with XPDL. Before we think of implementing it onto jBPM, is there any kind of progress there on your side? So we shoud not start from scratch. Also, with which version will you start: XPDL 1 or 2.0 (seems promising)?
I've seen Enyhdra Shark's implementation, and found that they also have a Wf-XML/ASAP service frontend (Interface 4 - Interoperability). Is it on the roadmap for jBPM?
Thanks for your answers.