[
https://jira.jboss.org/jira/browse/JBPM-1242?page=com.atlassian.jira.plug...
]
Miguel Valdes Faura updated JBPM-1242:
--------------------------------------
I was taking a look to the current APIs (ExecutionService, ManagementService and
ProcessService) and here are my first comments:
While I think its important to provide a unified API for PVM users I'm not sure
whether this is useful when developing process languages extensions.
Let me explain this point:
While i could see the interest of having a unified API for process deployment at PVM level
as well as XPDL, BPEL and JPDL process extensions, I'm still in doubt about how we
could do the same at Execution API level. startExecution and specially signalExecution
operations are indeed useful at PVM level but cannot be exposed to end users as an entry
point for XPDL or JPDL based projects (while instantiateProcess or startTask operations
are more appropriate).
My point is shall we consider that there is a unified API at PVM level that will be
leveraged by PVM end users (mainly developers wanted to add the PVM to their Java
application) as well as by end products (vertical solutions): XPDL, BPEL,JPDL, pageflow
based ?
My feeling is that each vertical solution (based on a particular process language) has
different requirements so seems hard to me to propose a unified API at this level...
publish pvm api and examples online
-----------------------------------
Key: JBPM-1242
URL:
https://jira.jboss.org/jira/browse/JBPM-1242
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: PVM
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: PVM 1.0 beta1
to get more community feedback
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira