[JBoss JIRA] Resolved: (JBPM-996) Add ESB Service Node to jpdl and jpdl-designer
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-996?page=com.atlassian.jira.plugi... ]
Thomas Diesler resolved JBPM-996.
---------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Out of date for all Tasks and Feature Requests created before 1-Jan-2008
> Add ESB Service Node to jpdl and jpdl-designer
> ----------------------------------------------
>
> Key: JBPM-996
> URL: https://jira.jboss.org/jira/browse/JBPM-996
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Environment: The ESB has an ESBActionHandler that can be manually configured at each node representing an ESB service in a jPDL processdefinition. A new node type of service-node, that is supported through the jpdl designer, would make it easier for the user to add these sevices, as the designer would know what properties are required for the user to provide.
> A nice thing about the ESB from a jBPM perspective (and an ESB Service Node) is that it gives jBPM access to practically any type of service through the same node-type, e.g., web services, rule services, jms queues, file transfer services, etc. So if jBPM has a service node, it eliminates the need to create lots of other specialized node types in jBPM, and less of a need for customers to create custom action handlers.
> Reporter: Jeff DeLong
>
--
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
16 years, 10 months
[JBoss JIRA] Resolved: (JBPM-966) Modify Hibernate mappings to enable searching for TaskInstance's by VariableInstance
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-966?page=com.atlassian.jira.plugi... ]
Thomas Diesler resolved JBPM-966.
---------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Out of date for all Tasks and Feature Requests created before 1-Jan-2008
> Modify Hibernate mappings to enable searching for TaskInstance's by VariableInstance
> ------------------------------------------------------------------------------------
>
> Key: JBPM-966
> URL: https://jira.jboss.org/jira/browse/JBPM-966
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.2.0
> Environment: Any
> Reporter: Richard Tomlinson
> Attachments: patches.zip
>
>
> We want to be able to *efficiently* search for task instances based on the values of one or more variable instance. For example:
> TaskInstance myTasklnstance = ....
> myTaskInstance.setVariableLocally("owner", "theOwner");
> myTaskInstance.setVariable("anId", new Long(123456));
> Using this example we would like to create a Hibernate Criteria based query that will allow us to search and retrieve the task instance using the two variables as criteria of the search. At present, this does not appear to be possible.
> Querying for TaskInstances based on one or more VariableInstance's requires a convoluted HQL expression where each variableinstance (v) is obtained with the join to task instance (ti) with "v.processInstance.id = ti.taskMgmtInstance.processInstance.id"
> Observation:
> -----------------
> TaskInstance hibernate mappings allows the retrieval of all variable instances for a given task instance. This mapping allows the resulting sql to join the JBPM_TASKINSTANCE table to JBPM_VARIABLEINSTANCE table. The JBPM_VARIABLEINSTANCE table has a FK back to JBPM_TASKINSTANCE but the Hibernate mappings do not contain the correponding reverse mapping.
--
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
16 years, 10 months
[JBoss JIRA] Resolved: (JBPM-955) jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBPM-955?page=com.atlassian.jira.plugi... ]
Thomas Diesler resolved JBPM-955.
---------------------------------
Fix Version/s: (was: jBPM 3.3.2 GA )
Resolution: Out of Date
Out of date for all Tasks and Feature Requests created before 1-Jan-2008
> jBPM: support setting Actor or Swimlane on process level (to re-use sub-processes)
> ----------------------------------------------------------------------------------
>
> Key: JBPM-955
> URL: https://jira.jboss.org/jira/browse/JBPM-955
> Project: JBoss jBPM
> Issue Type: Feature Request
> Components: Core Engine
> Affects Versions: jBPM 3.2.0
> Environment: All
> Reporter: Arjan van Bentem
> Priority: Minor
>
> Currently, an Actor or Swimlane is assigned within the task definition. When using sub-processes it would be very convenient to make the assignments in the parent process, such as in the parent <process-state>, or maybe even in the outermost <process-definition>.
> For example: both a helpdesk employee and the customer would need to fill in the same questionnaire at different points in the main process. The steps to fill in the questionnaire would be a generic sub-process, in which (at design time) one would not know the Swimlane nor Actor. This would require a way to set the swimlane in the parent's process-state:
> <!-- multiple references to the same sub-process, for different swimlanes -->
> <process-state name="Customer survey" swimlane="client">
> <sub-process name="survey" />
> </process-state>
> :
> :
> <process-state name="Employee survey" swimlane="employer">
> <sub-process name="survey" />
> </process-state>
> ... or
> <process-state name="Employee survey">
> <assignment actor-id="..."/>
> <sub-process name="survey" />
> </process-state>
> ... or maybe even at an even higher level, where jBPM would iterate up into the chain, possibly though nested sub-processes, until some assignment is found?
--
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
16 years, 10 months