[JBoss JIRA] Created: (JBPM-2896) Could you add the name of the task in HistoryTask ?
by Jaber C. Mourad (JIRA)
Could you add the name of the task in HistoryTask ?
---------------------------------------------------
Key: JBPM-2896
URL: https://jira.jboss.org/browse/JBPM-2896
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.3
Environment: Jbpm 4.4 snapshot
Reporter: Jaber C. Mourad
Fix For: jBPM 4.4
Hi,
As HistoryTaskQuery permit to make some fine requests to HistoryTask, If I want to enumerate some data from historytask, I need to have the name of the task...
This is the only missed data compared to Task interface...
I don't know if it is possible to add it in the 4.4 version, but it will be great !
Regards
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBPM-2920) Choose N tasks out from M paths in fork nodes
by Jecoso Chou (JIRA)
Choose N tasks out from M paths in fork nodes
----------------------------------------------
Key: JBPM-2920
URL: https://jira.jboss.org/browse/JBPM-2920
Project: jBPM
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Environment: JBOSS 5.1GA, JBPM 4.4,
Reporter: Jecoso Chou
Fix For: jBPM 4.5
For example:
<fork name="fork1">
<transition name="to A" to="A">
</transition>
<transition name="to B" to="B">
</transition>
<transition name="to C" to="C">
</transition>
<transition name="to D" to="D">
</transition>
</fork>
This issue means that when process to this fork, only some of this 4 transition can be chosen to go,
for example ,the transition "to A" and "to A".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBPM-2911) Possible performance problem caused by autoSaveProcessInstances
by Alejandro Guizar (JIRA)
Possible performance problem caused by autoSaveProcessInstances
---------------------------------------------------------------
Key: JBPM-2911
URL: https://jira.jboss.org/browse/JBPM-2911
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 3.2.5.SP5
Reporter: Alejandro Guizar
Fix For: jBPM 3.2.10
autoSaveProcessInstances is a List type field of JbpmContext class, which contains the processInstance needed to persistent to database.
List autoSaveProcessInstances = null;
Due to the List type of autoSaveProcessInstances, the same processInstance can be repeatedly added to autoSaveProcessInstances by JbpmContext.addAutoSaveProcessInstance method.
public void addAutoSaveProcessInstance(ProcessInstance processInstance)
{
if (autoSaveProcessInstances == null)
autoSaveProcessInstances = new ArrayList();
autoSaveProcessInstances.add(processInstance);
}
When invoked by JbpmContext.close method, JbpmContext.autoSave will iterate each processInstance in the autoSaveProcessInstances to save, thus the processInstance be saved repeatedly.
void autoSave()
{
if (autoSaveProcessInstances != null)
{
Iterator iter = autoSaveProcessInstances.iterator();
while (iter.hasNext())
{
ProcessInstance processInstance = (ProcessInstance)iter.next();
save(processInstance);
iter.remove();
}
}
}
In a web app based on seam 2.2.0, jbpm 3.2.5.sp5, a jsf request will cause the same processInstance to be saved more than 2000 times. The suggestion is to change the type of autoSaveProcessInstances from List to Set.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (JBPM-2386) Update description of DeployProcessTask
by Toshiya Kobayashi (JIRA)
Update description of DeployProcessTask
---------------------------------------
Key: JBPM-2386
URL: https://jira.jboss.org/jira/browse/JBPM-2386
Project: JBoss jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 3.2.5.SP5
Reporter: Toshiya Kobayashi
Chapter 21.1.1 of the User Guide states:
============
<target name="deploy.par">
<taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask">
<classpath --make sure the jbpm-[version].jar is in this classpath--/>
</taskdef>
<deploypar par="build/myprocess.par" />
</target>
To deploy more process archives at once, use the nested fileset elements. The file attribute itself is optional. Other attributes of the ant task are:
* cfg: cfg is optional, the default value is 'hibernate.cfg.xml'. The hibernate configuration file that contains the jdbc connection properties to the database and the mapping files.
* properties: properties is optional and overwrites *all* hibernate properties as found in the hibernate.cfg.xml
* createschema: if set to true, the jbpm database schema is created before the processes get deployed.
============
http://docs.jboss.org/jbpm/v3.2/userguide/html_single/#theprocessarchive
But this description is old now. They should be:
=============
<target name="deploy.par">
<taskdef name="deploypar" classname="org.jbpm.ant.DeployProcessTask">
<classpath --ensure jbpm-[version].jar is in this classpath--/>
</taskdef>
<deploypar process="build/myprocess.par" />
</target>
To deploy more process archives at once, use the nested fileset elements. The process attribute itself is optional. Other attributes of the ant task are:
* jbpmcfg: Optional, the default value is jbpm.cfg.xml. The JBPM configuration file can specify the location of Hibernate configuration file ( the default value is hibernate.cfg.xml ) that contains the jdbc connection properties to the database and the mapping files.
=============
--
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
14 years, 4 months
[JBoss JIRA] Created: (JBPM-2850) Column sorting broken in console tables
by M M (JIRA)
Column sorting broken in console tables
---------------------------------------
Key: JBPM-2850
URL: https://jira.jboss.org/jira/browse/JBPM-2850
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Console
Affects Versions: jBPM 4.0, jBPM 4.1, jBPM 4.2, jBPM 4.3
Reporter: M M
Clicking on column headers in tables causes the contents of those tables to be sorted. However, sorting on columns that contain numbers appears to be broken. For example, given "1,3,5,8,10,11,13,20", it will sort as "1,10,11,13,20,3,5,8". Sorting of other (string) columns works fine.
I would also recommend that tables containing data with logically-composite keys be sorted by multiple columns, with the column selected for sorting being the first key by which the rows are sorted. For example, "Process Definitions" could be sorted by Name, then by Version. That would make it easy to find the latest version of a given process definition.
--
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
14 years, 5 months