[jbpm-issues] [JBoss JIRA] Commented: (JBPM-2307) prune api where possible
[
https://jira.jboss.org/jira/browse/JBPM-2307?page=com.atlassian.jira.plug...
]
Tom Baeyens commented on JBPM-2307:
-----------------------------------
We won't expose the hibernate session in the jbpm api as we might move to jpa later
on.
prune api where possible
------------------------
Key: JBPM-2307
URL: https://jira.jboss.org/jira/browse/JBPM-2307
Project: JBoss jBPM
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Runtime Engine
Reporter: Tom Baeyens
Assignee: Tom Baeyens
Fix For: jBPM 4.0
* especially the access to process definition objects can be minimized.
- setActivity on the execution interfaces should be removed for sure
- execution.fire must allow access to observable elements like activities, process
definition and transitions.
- it's good if activity behaviour implementations can access the transitions and
child activities structure
--
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