<div dir="ltr">Compliments for this work and nice to see JAXB introduced in the api. I
always wondered it it would be possible and how it would fit in. It
seems to be going in the direction of BPMN.<br><br>What I do not get
(yet) is the relation between the jaxb model in the api (it is internal
however) and jpdl 4. The api is outside jBPM but the PVM moved into
jBPM. Strange to me since the first is more related and the latter is
also used by the Bull people for their XPDL and BPEL solutions.<br>
<br>Ronald (finding out he has to spend some more time in the site/source/... these days.. and maybe less in the forum)<br><br>p.s. Sorry Thomas for the duplicate message you get, wrong sender in the initial message<br><br>
<div class="gmail_quote">On Tue, Jul 15, 2008 at 10:40 AM, Thomas Diesler <<a href="mailto:thomas.diesler@jboss.com">thomas.diesler@jboss.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Folks,<br>
<br>
I laid out the Mission of the API effort in<br>
<a href="http://jbpm.dyndns.org/jbpmwiki/index.php?title=APIMission" target="_blank">http://jbpm.dyndns.org/jbpmwiki/index.php?title=APIMission</a><br>
<br>
The terminology that we can use to discuss the abstract API constructs<br>
is nicely defined by the BPMN standard. Here I put together a glossary<br>
of terms <a href="http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMNGlossary" target="_blank">http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMNGlossary</a><br>
<br>
Much research has been done in BPM patterns that users of a BPM engine<br>
expect. These patterns I put together here<br>
<a href="http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMPatterns" target="_blank">http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMPatterns</a><br>
<br>
Of status of current support for these patters through the API is<br>
documented here<br>
<a href="http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedPatterns" target="_blank">http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedPatterns</a><br>
<br>
All this work really servers just a single purpose, which is to<br>
<br>
* clearly define what our mission is<br>
* lay out the path to follow in order to achieve that mission<br>
* have time bound milestones along the path (i.e. the release cycle)<br>
<br>
I hope that clarifies the BPM product direction and is an adequate basis<br>
from which individual tasks can be derived.<br>
<br>
cheers<br>
-thomas<br>
<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org" target="_blank">jbpm-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbpm-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
</blockquote></div><br></div>