[
http://jira.jboss.com/jira/browse/JBIDE-2237?page=comments#action_12419028 ]
Tom Baeyens commented on JBIDE-2237:
------------------------------------
in a first iteration. it would already be great if we could generate a jPDL process
skeleton from a BPMN process. it doesn't have to be complete. jPDL to BPMN is not
that important. that leads to round-tripping between disparate analysis and
implementation models, which is fundamentally a broken way of developing software.
a first step would be that the graph model would be exported from BPMN to jPDL. just the
nodes and transitions. you can use node type "node" for this, i think.
Koen, this brings up the issue of changing node types. BPMN activities will be converted
to "node"s and then in the jPDL editor, the developer can change the node type.
Is that a strategy that makes sense to you ? Is it hard to add it to jPDL 4 ?
BPMN plugin
-----------
Key: JBIDE-2237
URL:
http://jira.jboss.com/jira/browse/JBIDE-2237
Project: Tools (JBoss Tools)
Issue Type: Task
Components: jbpm
Reporter: Tom Baeyens
Assigned To: Marshall Culpepper
Fix For: 3.0.0.alpha
Attachments: stp-bpmn-pieces-jbt.txt, stp-bpmn-pieces-v2.txt,
stp-bpmn-pieces.txt
The STP BPMN modeller
http://www.eclipse.org/stp/bpmn/ should be bundled with the jPDL
process designer.
The idea is that business analysts will be able to create BPMN diagrams and save them in
the default (i believe it is XMI) file format.
The first goal would be that we're able to build that plugin and take it for a test
ride.
The next step could be to add an "Export to jPDL" feature to that BPMN
designer. That would then create a jPDL skeleton process that has to be further edited in
the GPD (jPDL editor plugin)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira