[JBoss JIRA] Created: (JBPM-2550) jbpm 4.1 Fork and Join gives some exception. Details given belo
by Makarand Kulkarni (JIRA)
jbpm 4.1 Fork and Join gives some exception. Details given belo
---------------------------------------------------------------
Key: JBPM-2550
URL: https://jira.jboss.org/jira/browse/JBPM-2550
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: jbpm 4.1, jboss 5.0 and GPD designer with eclipse packaged with jbpm 4.1
Reporter: Makarand Kulkarni
Fix For: jBPM 4.x
Hi,
JPDL ( SubProcessFill.jpdl )attached ( having fork,join with tasks ) with this ticket is giving following exception
org.jboss.resteasy.spi.UnhandledException: org.hibernate.LazyInitializationException: could not initialize proxy - no Session
Complete error stack is attached.
---
One of my requirement is to assign task( taskform) to multiple users and wait in the process till all users completes the filling of task form.
Tried subprocess but then taskform gets assigned to single user.
Also tried candidategroups. Same problem here.
Your help in this regard is highly appreciated.
Waiting for your reply.
-Regards
Makarand
--
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, 2 months
[JBoss JIRA] Created: (JBPM-2556) identify minimal runtime library dependencies
by Tom Baeyens (JIRA)
identify minimal runtime library dependencies
---------------------------------------------
Key: JBPM-2556
URL: https://jira.jboss.org/jira/browse/JBPM-2556
Project: jBPM
Issue Type: Task
Security Level: Public (Everyone can see)
Reporter: Tom Baeyens
Fix For: jBPM 4.x
feedback from a customer:
"
after trying hard today, I got jBPM4 running in OSGi equinox. I only tested a little functionality with a simple persistent jPDL workflow using HSQL in-memory db.
The problem was that the SAXFactory provider could not be configured properly and resulted in a classloader violation exception.
Solution was actually simple:
I removed all 3rd party libraries that have something to do with XML (e.g. xml-apis.jar) and ship with jBPM4 and from the bundle-classpath.
Now I wonder, if the JBPM4 team has an overview of the necessary smallest dependency set for 3rd-party libs in order to OSGi-tify jBPM and these dependend-jars and get the unnecessary rubbish out of the classpath.
Hope they can provide some feedback about that.
------------------
I forgot to send you my current MANIFEST which is working with the small example:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: WFTEST
Bundle-SymbolicName: WFTEST
Bundle-Version: 1.0.0.qualifier
Bundle-Activator: wftest.Activator
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Import-Package: org.osgi.framework;version="1.3.0"
Bundle-ClassPath: lib/activation.jar,
lib/antlr.jar,
lib/avalon-framework.jar,
lib/commons-collections.jar,
lib/commons-logging.jar,
lib/dom4j.jar,
lib/ejb3-persistence.jar,
lib/hibernate-annotations.jar,
lib/hibernate-cglib-repack.jar,
lib/hibernate-commons-annotations.jar,
lib/hibernate-core.jar,
lib/hibernate-entitymanager.jar,
lib/hsqldb.jar,
lib/idm-api.jar,
lib/idm-common.jar,
lib/idm-core.jar,
lib/idm-hibernate.jar,
lib/idm-spi.jar,
lib/javassist.jar,
lib/jaxb-api.jar,
lib/jaxb-impl.jar,
lib/jboss-common-core.jar,
lib/jboss-j2ee.jar,
lib/jboss-logging-spi.jar,
lib/jbosscache-core.jar,
lib/jbpm-console-form-plugin.jar,
lib/jbpm-console-graphView-plugin.jar,
lib/jbpm-console-integration.jar,
lib/jbpm-console-reports.jar,
lib/jbpm-examples-tests.jar,
lib/jbpm-jboss4.jar,
lib/jbpm-jboss5.jar,
lib/jbpm-spi.jar,
lib/jbpm-test-db-tests.jar,
lib/jbpm-tomcat6.jar,
lib/jbpm.jar,
lib/jgroups.jar,
lib/jta.jar,
lib/jtds.jar,
lib/juel-engine.jar,
lib/juel-impl.jar,
lib/juel.jar,
lib/junit.jar,
lib/livetribe-jsr223.jar,
lib/log4j.jar,
lib/logkit.jar,
lib/mail.jar,
lib/mysql-connector-java.jar,
lib/postgresql.jar,
lib/servlet-api.jar,
lib/slf4j-api.jar,
lib/slf4j-jdk14.jar,
lib/slf4j-log4j12.jar,
lib/standalone-compiler.jar,
lib/subethasmtp-smtp.jar,
lib/subethasmtp-wiser.jar,
.
I guess several of these jars could be removed and the remaining could be wrapped in OSGi-Bundle jars.
------------------
"
--
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, 2 months
[JBoss JIRA] Created: (JBPM-2801) Support querying for Tasks by their executionId
by Per Christian Henden (JIRA)
Support querying for Tasks by their executionId
-----------------------------------------------
Key: JBPM-2801
URL: https://jira.jboss.org/jira/browse/JBPM-2801
Project: jBPM
Issue Type: Patch
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.x
Reporter: Per Christian Henden
Fix For: jBPM 4.x
I have a case where I need to look up tasks in an EventListener.
What's available to me is the EventListenerExecution (ExecutionImpl).
I found no simple way of doing this. The attched patch adds the ability to query by executionId in a TaskQuery, exactly like in a HistoryTaskQuery.
The simplest way to do this today (as far as I know) is:
DbSession taskDbSession = EnvironmentImpl.getFromCurrent(DbSession.class);
Task = taskDbSession.findTaskByExecution(execution);
I dislike using the DbSession object this way, it would be better to use the JBPM API.
Using HistoryTaskService (which is part of the API) is possible, but is too much work:
//Find all tasks related to the current execution
final List<HistoryTask> relatedTasks = processEngine.getHistoryService().createHistoryTaskQuery().executionId(execution.getId()).list();
//Find all active tasks of the current execution
final List<HistoryTask> activeTasks = new ArrayList<HistoryTask>();
for (HistoryTask ht : relatedTasks) {
if (ht.getState() == null) {
activeTasks.add(ht);
}
}
if (activeTasks.size() > 1) {
throw new IllegalStateException("Got multiple matching tasks!");
} else if (activeTasks.isEmpty()) {
throw new IllegalStateException("Got no matching tasks!");
}
return activeTasks.get(0);
With the new code:
Task t = processEngine.getTaskService().createTaskQuery().executionId(execution).uniqueResult();
--
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, 2 months
[JBoss JIRA] Created: (JBPM-2952) History task not marked completed for tasks not associated with a process
by Jon Kranes (JIRA)
History task not marked completed for tasks not associated with a process
-------------------------------------------------------------------------
Key: JBPM-2952
URL: https://jira.jboss.org/browse/JBPM-2952
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: jBPM 4.4
Reporter: Jon Kranes
If a task is created programmatically directly from the TaskService API using TaskService.newTask, and is thus not associated with any process, a corresponding row in jbpm4_hist_task is created. However, when this task is marked as completed, using TaskService.completeTask, the task is deleted from jbpm4_task (as expected) but the row in jbpm4_hist_task does not get updated to set the state_ column value to 'completed'. As a result, this task does not get included in any HistoryTaskQuery results when .status("completed") is specified.
--
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, 2 months
[JBoss JIRA] Created: (JBPM-2936) Creating a subtask throw API should inherit properties from supertask
by Jimmy Smith (JIRA)
Creating a subtask throw API should inherit properties from supertask
---------------------------------------------------------------------
Key: JBPM-2936
URL: https://jira.jboss.org/browse/JBPM-2936
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.4
Reporter: Jimmy Smith
Fix For: jBPM 4.5
When creating a subtask in java code using taskService.newTask(parentTask.id), the executionId and processInstanceId fields are left blank in the database.
Seeing that the task interface also does not provide a 'getParentTask' method, it means that there is no way to get the execution or processInstance from within the task without maybe casting it to a TaskImpl, which defies the purpose of using interfaces in the first place.
As an example, we have a task with a timer set on a duedate. If the timer fires, a java class is executed that will create a subtask for a supervisor to follow up (why was the original task not completed on time?) while leaving the original task intact and in the same activity (we do not want a state transition to a new activity).
As it is now, we cannot do this programming against the interface API, we have to cast objects and that also complicates unit testing.
Subtasks by implication should have at least the same processInstance as the parent task, execution is debatable.
--
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, 2 months
[JBoss JIRA] Resolved: (JBPM-1211) complete software logging
by HuiSheng Xu (JIRA)
[ https://jira.jboss.org/browse/JBPM-1211?page=com.atlassian.jira.plugin.sy... ]
HuiSheng Xu resolved JBPM-1211.
-------------------------------
Fix Version/s: (was: jBPM 4.x)
Resolution: Out of Date
> complete software logging
> -------------------------
>
> Key: JBPM-1211
> URL: https://jira.jboss.org/browse/JBPM-1211
> Project: jBPM
> Issue Type: Feature Request
> Reporter: Tom Baeyens
>
> complete the docs and implementation for software logging.
> 1) review the defaults.
> 2) verify the correct operation of the exception logger. this is a log handler that will keep the last x-hundred logs in a circular buffer. when an exception occurs, it will flush it's buffer (+the exception report) in a file. this can definitely boost performance and improve the problem reports that we'll get in afterwards as users can specify a debug log level for this without a significant performance penalty (except for the string concatenations)
> See also java.util.logging.MemoryHandler, but I believe I have found that insufficient on a previous look.
--
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, 2 months