*push*
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4258246#4258246
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4258246
___
jboss-user mailing list
jboss-user@lists.jboss.o
It seems strange to me that are just a few people interested in this topic
although the situation described seems to me very common. Are there still so
few people working with 4.x or has nobody run across the problem? If you have
it would be great to count on your vote in JIRA.
View the origina
I commented on this again since I consider this really important because at the
moment it makes you change your process model for escalations which is probably
not wanted. If this was possible in 3.x this would also lead to problems when
migrating from 3.x to 4.x, right?
Regarding the behaviour
hmm... JBPM-2537 is targeted at 4.3, I saw you added your vote to it. Great now
gather others to do the same to increase the chance of it getting fixed quicker
-;)
I'm not sure what the default behaviour in jBPM 3 is, if that is to end
(cancel) the task, the same should happen here, without hav
No problem, I did not succeed either in finding it on JIRA. Forgot to mention I
tried searching JIRA. Thanks for your effort. I really hope this will be fixed
in 4.2.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257978#4257978
Reply to the post :
http://
Thanks and sorry... while I was reading your jira issue I DID find the other
one (not sure why it did not show up earlier)
https://jira.jboss.org/jira/browse/JBPM-2537
So I'll close yours as a duplicate. Again, sorry
View the original post :
http://www.jboss.org/index.html?module=bb&op=vie
Here we go:
https://jira.jboss.org/jira/browse/JBPM-2559
I did not write a lot since there is a link to the forum post and I supplied a
process definition and the unit test.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257963#4257963
Reply to the post :
Hmmm I thought I already responded.
To me it is a bug, but others might think not so (not sure what their arguments
would be).
please file a jira issue, I do not seem to be able to find one
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257894#4257894
Reply
I'd really like having some feedback on this since for me questions arise:
- Is this behaviour just not desired from my point of view but conform to the
processs excecution model in jBPM?
- Is this a bug since there is a task in somebody's task list which cannot be
completed nor deleted? It can
Okay, thanks for all the hints. It was really due to a classpath problem.
Here's what I found:
Logging and using Tom's hint with the DBManager showed that there was a query
for an execution which did not exist anymore. Before the executing of the job
(transition with timer to task "escalation"
configuration file looks good.
maybe you have multiple logging.properties files on your classpath. check that
you have only one.
another thing that you can do when you are in your ide is put this text in your
Display window:
org.hsqldb.util.DatabaseManager.main(new String[]{})
|
select it
I don't manage to turn up the loglevel. Any hints?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257632#4257632
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257632
___
jbos
I must be doing something wrong since I don't see more in the log.
| handlers= java.util.logging.ConsoleHandler
| redirect.commons.logging = enabled
|
| java.util.logging.ConsoleHandler.level = FINEST
| java.util.logging.ConsoleHandler.formatter =
org.jbpm.internal.log.LogFormatter
I am going to turn up the loglevel. The process was deployed with just one
timer, does not change anything. The duplicate timers are due to the GPD bug
already reported in JIRA.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257458#4257458
Reply to the post
ok, and I only now see there are 3 identical timers on the transition. Can you
remove those and also turn up the loglevel when running the unittest.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257457#4257457
Reply to the post :
http://www.jboss.org/index.
There is an additional task to complete afterwards which I have not completed
so the process should not be ended. I am doing an
assertTrue(processInstance.isActive("task2"));
in the unit test and it does not fail.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopi
might be because the process is actually already ended Can you check?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257316#4257316
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257316
Full Stacktrace ..
| ### EXCEPTION ###
| 11:00:39,186 INF | [DefaultCommandService] exception while executing
command org.jbpm.pvm.internal.cmd.completetask...@1c01ba9
| org.hibernate.ObjectNotFoundException: No row with the given identifier
exists:
I'll have a look into JIRA and I will verify that I am not mixing up files from
different versions. But what about my actual problem (see my last post). How do
I get rid of the task which is not needed anymore?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=42
there was a change in the businesscalendar config afaik between 4.0, and 4.1
(or was it towards 4.2, not fully sure). Did you change versions? If so, search
the jira for the related task and see if it is the possible cause.
View the original post :
http://www.jboss.org/index.html?module=bb&op=v
I do not know what exactly is the problem with the BusinessCalendar but I
created my process and my unit test within the examples project and the error
has gone away. Now back to the actual goal.
Please disregard my old post since there were some mistakes and things missing.
My process definiti
I must be doing something wrong. I took the unit tests of the supplied examples
as a base (regarding configuration files) which always worked fine for and I
created my process and my tests. The problem is that an exception is thrown:
| 12:03:47,093 FIN | [ProcessDefinitionImpl] creating new e
Yes I think you do need that. Would be nice if you made a unit test first to
test if that really works. I think it does, but not completely sure.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257102#4257102
Reply to the post :
http://www.jboss.org/index.htm
Thanks for your interesting answer, Ronald. I think for know I use the
timer/transitition approach because I need I want to visualize the escalation
in the diagram shown in the console. So it would be necessary to call a
completeTask() for the "old task" manually to remove it from the first user
oh, in addition, in 4 the tasks remains open, also not what you want I think.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257066#4257066
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257066
"The European guy" wrote : I managed to use a timer to make the engine take a
timeout transition after some time. My question here: If you make the engine
take the transition like this is the previous task completed? Or is this the
wrong approach and I should just change the assignment of the ta
Regarding the task lifecyle I have not written anything since I have not yet
looked into this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4257061#4257061
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4257061
___
Thanks for this really long answer, Ronald. In my opinion you are right,
escalation is a very complex thing and can mean a lot and I appreciate the
flexibility of jBPM but maybe we should think of a basic thing to be included
with the distro while replacing it with your own implementation is sti
One day late, and afternoon already since this response required a little
digging for me :-)
In theory you are right, escalating is a basic BPM-thing
In practical situations howeever, escalation differs from company to company,
department to department etc... and if you have a look at
http:/
Okay, I just went over the specific part of the article again and to me it
seems it is possible. It just seems to me that is a bit too much code for a
basic BPM-thing as an escaltion is one.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4256809#4256809
Reply
30 matches
Mail list logo
