Done.
Jira: http://jira.jboss.com/jira/browse/JBPM-669
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3948557#3948557
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3948557
___
Greetings.
When the end-tasks attribute is set to true leaving the task-node causes all
pending tasks to end, even tasks that are associated with different nodes.
| public void removeTaskInstanceSynchronization(Token token) {
| TaskMgmtInstance tmi = getTaskMgmtInstance(token);
|
Greetings. As part of our JBPM integration effort, I need to view the JBPM
Process Log in our application. I can do that without a problem, but the
process log output (which is returned by ProcessLog.toString()) is, umm, not
aestetically pleasing (i.e., it's UGLY).
I would really like to
Also posted to JIRA http://jira.jboss.org/jira/browse/JBPM-288
| ?xml version=1.0 encoding=UTF-8?
| process-definition
| xmlns=urn:jbpm.org:jpdl-3.1
| name=simple
|start-state name=start
| transition name= to=fork1/transition
|/start-state
|end-state
You specify the due date in the process definition as a duration (e.g., 2
hours), and when the task instance is created it converts it to the actual
date/time. You can use TaskInstance.getDueDate() to retrieve the calculated
date.
View the original post :
That's exactly what I am doing.
I am inserting the due date (duration) in the process definition as BOTH the
task instance due date AND the expriration time on a timer on the task. The
absolute due date (i.e., a real date) shows in the UI and my task fires when
the due date expires.
View the
Yes, this looks like the same issue (
http://jira.jboss.org/jira/browse/JBPM-288 ).
My contention is that when a join node reactivates the parent token, all child
tokens at that join node should be ended. The same is probably true for child
tokens that arrive at the join after the parent has
Ah ha! I restructured the process definition so that the task and timer
converge at an intermediate node and then proceed to the join:
| ?xml version=1.0 encoding=UTF-8?
| process-definition xmlns:jpdl=http://jbpm.org/3/jpdl;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
|
anonymous wrote : my expectation was that a join needs as many incomming tokens
as there were in the corresponding fork
The revised process definition satisifies that requirement, and the transition
out of the join is taken. I'm just wondering about the fate of the child tokens
after the
I have a workflow that forks into two branches and are later joined.
| ?xml version=1.0 encoding=UTF-8?
| process-definition xmlns:jpdl=http://jbpm.org/3/jpdl;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://jbpm.org/3/jpdl
Greetings. We have the need to attach descriptive information to a process
instance that is always available for the life of the process instance. My
first thought is to add a comment to the root token immediately after creating
the process instance.
Is the root token guaranteed to exist for
I am doing that (settng the authenticated user id with JbpmContext.setActorId())
However, when I pull the logs, the actorId field is always null. I've combed
through the source, and I don't see anyway to record the current authenticated
actor in the log record (i.e., ProcessLog).
For example,
That's exactly what I am doing:
| authenticate = jbpmContext.getServices().getAuthenticationService();
| ((DefaultAuthenticationService)authenticate).setActorId(whatever);
| /* --snip --*/
| jbpmContext.setActorId(SecurityHelper.getAuthenticatedActorId());
|
Yet, when I get the logs,
I recently looked at the security framework in 3.1, and I am a little confused.
The interface org.jbpm.security.AuthenticationService does not include a method
to set the authenticated actor id.
That means I cannot do something like
| AuthenticationService authenticate =
On a related note ...
When I retrieve ProcessLogs for a process instance, the actorId field is
always null. I expected that setting actorId on the JbpmContext would propagate
into the process logs, but that doesn't seem to be the case.
I need the log to include who (which actor) initiated a
Greetings. I have scoured the docs for JBPM 3.1, but cannot find a definitive
answer to this
Has JSF EL replaced BeanShell for transition expressions? Or is it simply an
option?
Thanx.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3926867#3926867
The 3.1 User's Guide refers to BeanShell scripts in several places (e.g.,
Section 9.5.5 -Script actions and Section 16.4.17 - Script expressions. Should
all those references be replaced by JSF EL ?
Also, would it be possible to post some more examples of using the Expression
Language? For
Nope, String[] did NOT work:
| 14:39:14,851 ERROR FieldInstantiator : couldn't parse the bean property
value 'VarListApproved|Boolean|False/VarList
| ' to a '[Ljava.lang.String;'
| 14:39:14,851 ERROR FieldInstantiator : couldn't parse set field 'VarList'
to value
Got it!!
The field xml to populate a List must be specified as
| node name=InitializeVariables
| action class=com.olf.workflowmgr.action.VariableInitActionHandler
| VarList
| elTranNum|Int|/el
| elInExcession|Boolean|False/el
|
I have an action that requires a List property to be populated in the process
definition.
| node name=InitializeVariables
| action class=com.olf.workflowmgr.action.VariableInitActionHandler
| VarListTranNum|Int|/VarList
| VarListInExcession|Boolean|False/VarList
|
This week I migrated my app to 3.1b1, and the externally produced process
definition xml deployed successfully. I haven't yet tried to run an instance of
the definition, though.
I also loaded up GPD 3.0.6, which allowed me to move the graphic elements as
expected. However, there were some
Can I simply unpack the GPD 3.0.6 feature and plug-in directory over my
existing 3.0.5 Eclipse directory?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3916661#3916661
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3916661
Greetings. I need to upgrade (migrate) my 3.0.2 database (Oracle) to the new
3.1 shema. There have been several statements on this forum that a tool for
doing this would be provided, but I have not found anything to do this.
Pointers? Thanx.
View the original post :
Greetings. After evaluating 3.0.2, I would like to continue development using
the latest and (hopefully) greatest 3.1 version. In the release notes there is
a reference to migration tips:
anonymous wrote : Configuration: The jbpm.properties file is replaced by a file
called jbpm.cfg.xml. The
Greetings! I am building a process definition in jpdl from our own application,
and need to deploy it in jbpm.
If I follow the instructions in
http://www.jboss.com/index.html?module=bbop=viewtopict=71393
I get a graph with all elements in the top left, but I cannot resize or
relocate anything
I tried that last tip (start a new process definition, and past in externally
created XML). The result was a graph diagram with all the elements drawn on top
of themselves.
I could grab some of the labels (transitions, I think) but I could not resize
or move the nodes.
To reiterate: I have
Greetings. I would like to be able to delete a process instance on the fly.
When I call GraphSession.deleteProcessInstance(), I get the following error:
| 12:53:37,347 ERROR JbpmSession : org.hibernate.ObjectDeletedException:
deleted object would be re-saved by cascade (remove deleted object
Solved. My application communicates with JBPM via Rendezvous (Tibco) messages.
I was incorrectly passing a JNI environment pointer (JNIEnv*) through the
callback to the listening thread. You need to maintain or create a pointer to
the JVM, and allocate a new JNIENV pointer in each thread.
Who
No, I don't lock the process instance. (Should I ?)
Could anyone summarize (1) when I would need to lock a process instance and (2)
when I should be saving a process instance to the datbase?
Thanx.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3913412#3913412
Process Definition:
| ?xml version=1.0 encoding=UTF-8?
|
| process-definition
| xmlns=http://jbpm.org/3/jpdl;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://jbpm.org/3/jpdl
http://jbpm.org/xsd/jpdl-3.0.xsd;
| name=ValidateDeal
|
|
I couldn't find this bug in the jira, and it is causing me major grief. Can
anyone confirm that it has been filed as a bug?
Also, I looked at the schema and don't really understand what is causing this
error.
anonymous wrote :
| The matching wildcard is strict, but no declaration can be
It seems that the schema for assignment should be ...
| xs:element name=assignment
| xs:annotation
| xs:documentationControls the behavior of assigning a
task to an identity./xs:documentation
| /xs:annotation
| xs:complexType
Finally found this in jira:
http://jira.jboss.com/jira/browse/JBPM-430
It claims to be fixed in 3.1a, but it apparently has not made it back to 3.0.x
Can the correct xsd be posted your web site (as specified in the
processdefinition xml) ?? Thanx.
View the original post :
Greetings. I have built a java app that invokes JBPM and communicates with our
core application. I have also deployed a real-world prototype process
definition. All is working pretty much as expected, except ... every so often
JBPM stops responding. This happens in various places, but most
Greetings. I have deployed the following process definition:
| ?xml version=1.0 encoding=UTF-8?
|
| process-definition
| xmlns=http://jbpm.org/3/jpdl;
| xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
| xsi:schemaLocation=http://jbpm.org/3/jpdl
anonymous wrote :
| it depends how you deployed the process and the actionhandlers. Are both
versioned in the same .par file? If so are you sure the right class got in the
.par file. If it was not refreshed, it could be the wrong version.
|
I am reading the processdefinition.xml file from
Greetings. I was wondering if there is an API to tidy up the database. For
example, to delete process instances that completed before a given date, remove
process definitions that are obsolete and have no active instances, etc.
Thanx.
View the original post :
I am modifying and reimporting a process definition. If I look in the database
table, I see that all the entires have the same version number (-1). Is this
normal?
Is there something else required to track versions of process definitions?
Thanx.
View the original post :
Problem solved (replaced by new problem).
The process instance was being created with the wrong process definition,
because my process definitions are not being properly versioned when they are
imported like this:
| public void initProcessDefinitions() {
| JbpmSession
Greetings. I am trying to write an action handler that has a String field which
is populated from the process definition.
state name=Run Script 1
| transition name=GotoScript2 to=Run Script 2/transition
| event type=node-enter
| action name=RunAvsScript1
40 matches
Mail list logo
