AW: [jbpm-dev] GPD integration

[Bernd Rücker]

Hi.

I may be mistaken, but isn't the GPD the designer for a concrete language
(e.g. jPDL 3 or jPDL 4). How can this be made generic?

The API could be used for deployment or things like that, but not for the
designer itself. Or not?

Cheers
Bernd

-----Ursprüngliche Nachricht-----
Von: jbpm-dev-bounces at lists.jboss.org
[mailto:jbpm-dev-bounces at lists.jboss.org] Im Auftrag von Thomas Diesler
Gesendet: Montag, 24. November 2008 09:27
An: Koen Aers
Cc: jbpm-dev at lists.jboss.org; Mark Little
Betreff: [jbpm-dev] GPD integration

Hi Koen,

in Antwerp we talked about the GPD not having a direct dependency on the
jBPM4 code base but rather on the API that exposes the concepts that
jBPM4 should implement. By providing support for the jBPM3 threading
model the basic concepts that we talked about are applicable to the
jBPM3 code base as well.

If the API is the integration point for the GPD (btw this argument holds
true for the GWT Console as well) it should be possible to implement a
single GPD code base that works across jBPM versions. The API would
become the common base were all integration concerns would come
together. In this light the term SPI is probably even more applicable.

Thoughts?

cheers
-thomas

--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
BPM Product Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
jbpm-dev mailing list
jbpm-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev