]
Koen Aers updated GPD-192:
--------------------------
Component/s: jpdl
Remove need for jBPMRuntime in jDPL Designer
--------------------------------------------
Key: GPD-192
URL:
https://jira.jboss.org/jira/browse/GPD-192
Project: JBoss jBPM GPD
Issue Type: Feature Request
Components: jpdl
Reporter: Jeff DeLong
Assignee: Koen Aers
jPDL designer should be enhanced to not require the entire jBPM suite download to be
configured as the jBPM Runtime, but instead include bpm-jpdl.jar, version.xml and whatever
other files are required in a jBPM library which could be included as part of the plugin
installation. Currently the jpdl designer requires this design tool to have access to jbpm
source code, etc, which many process designers would not typically have. It also will make
it easier packaging for the SOA-P.
Also, the drools plugin has a feature that allows the user to take an existing project
and "Convert to Drools Project", which essentially adds the drools library jars
to the project classpath. This is a really handy feature, because it does not force
developers to start out as a drools project (which project type should I use if I want to
include both jbpm and drools?). It would be nice if jPDL designer had a similar
capability, where you could just say "Convert to jBPM Project", and it added the
jbpm library jars to the classpath. In this way the SOA Platform IDE plugins (jBPM and
Drools) would work in a similar way wrt to classpath, project structure, etc.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: