sparklehorse wrote : kukeltje wrote : Remaining question: did you upgrade
from a 3.1 version:
| |
| | http://jira.jboss.com/jira/browse/JBPM-854?
| |
| | Or use mysql 5.0?
| |
| | debugging the decisioncode requires adding a debug statement in the
source to see what
strange... these two bugs are ONLY (as in the report) when deployed against a
previous version. That is not the case here as you reported. That is why I did
not mention these to you. So probably these two reports are incomplete.
Thanks for letting me/us know
View the original post :
kukeltje wrote : did you search the forum (e.g. with google or the search
above on the left, small blue text))
|
| Has been discussed lots of times... first see if there is some info in
there.
|
| Besides that ALWAYS report you jboss version, db used, jdk
etc...etc...etc...
i'm a
I've tried without luck also a simplified scenario with all possible conditon
syntax
| decision name=CheckState
| transition name=tr2 to=node2
| conditionstatus=='DO NOT GO HERE'/condition
| /transition
Please, can anyone tell me what version of jBPM he is using, what appserver,
db, jdk, if he did upgrades etc?
Or tell him to e.g. look at the unittests where there are examples, or look in
the jira... (but watch out, he might loose a finger)
View the original post :
jboss 4.0.5.GA
JBPM 3.2.GA
JDK 1.5
thanks
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4057632#4057632
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4057632
___
jboss-user
Remaining question: did you upgrade from a 3.1 version:
http://jira.jboss.com/jira/browse/JBPM-854?
Or use mysql 5.0?
debugging the decisioncode requires adding a debug statement in the source to
see what gets evaluated.
View the original post :
Unittests are great to reproduce issues instead of snippets (should be well
known to ahhh never mind). The following unittest runs fine in the cvs head
of 21-06-2007
package org.jbpm.jpdl.el;
|
| import junit.framework.TestCase;
|
| import org.jbpm.JbpmException;
| import
oh and btw, this one does as well. (no expression)
| package org.jbpm.jpdl.el;
|
| import junit.framework.TestCase;
|
| import org.jbpm.JbpmException;
| import org.jbpm.graph.def.ProcessDefinition;
| import org.jbpm.graph.exe.ProcessInstance;
|
| public class
kukeltje wrote : Remaining question: did you upgrade from a 3.1 version:
|
| http://jira.jboss.com/jira/browse/JBPM-854?
|
| Or use mysql 5.0?
|
| debugging the decisioncode requires adding a debug statement in the source
to see what gets evaluated.
no upgrade, just fresh install
sparklehorse wrote :
| no upgrade, just fresh install of all the stuff
| but i'm using mysql 5.0
|
|
| i've also tried to change, even if i don't see any error,
| every bit(1) in the mysql schema to tinyint(1)
| ...same result
|
ok, thanks for letting me know
sparklehorse
did you search the forum (e.g. with google or the search above on the left,
small blue text))
Has been discussed lots of times... first see if there is some info in there.
Besides that ALWAYS report you jboss version, db used, jdk etc...etc...etc...
View the original post :
12 matches
Mail list logo
