LOL
now i realize this was probably only posted on the mailing list.
so we need to get that overview of which list/forum is to be used for what asap :-)
regards, tom.
Tom Baeyens wrote:
ronald, if possible, please reply on the forum.
I would like all discussions to be held there. otherwise some parts of
discussions are held on mailing list only and others on forum. Then it
gets unclear which discussion medium should be used.
regards, tom.
Ronald van Kuijk wrote:
> 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.
>
> 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.
>
> Ronald (finding out he has to spend some more time in the
> site/source/... these days.. and maybe less in the forum)
>
> p.s. Sorry Thomas for the duplicate message you get, wrong sender in
> the initial message
>
> On Tue, Jul 15, 2008 at 10:40 AM, Thomas Diesler
> <thomas.diesler(a)jboss.com <mailto:thomas.diesler@jboss.com>> wrote:
>
> Folks,
>
> I laid out the Mission of the API effort in
>
http://jbpm.dyndns.org/jbpmwiki/index.php?title=APIMission
>
> The terminology that we can use to discuss the abstract API
> constructs
> is nicely defined by the BPMN standard. Here I put together a
> glossary
> of terms
http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMNGlossary
>
> Much research has been done in BPM patterns that users of a BPM
> engine
> expect. These patterns I put together here
>
http://jbpm.dyndns.org/jbpmwiki/index.php?title=BPMPatterns
>
> Of status of current support for these patters through the API is
> documented here
>
>
http://jbpm.dyndns.org/jbpmwiki/index.php?title=JBPM3SupportedPatterns
>
> All this work really servers just a single purpose, which is to
>
> * clearly define what our mission is
> * lay out the path to follow in order to achieve that mission
> * have time bound milestones along the path (i.e. the release cycle)
>
> I hope that clarifies the BPM product direction and is an adequate
> basis
> from which individual tasks can be derived.
>
> cheers
> -thomas
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev(a)lists.jboss.org <mailto:jbpm-dev@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbpm-dev