-
1. Re: Problems with conditions in transactions
fjfernandez Oct 10, 2006 2:40 AM (in response to fjfernandez)Anybody can help me?
-
2. Re: Problems with conditions in transactions
kukeltje Oct 10, 2006 5:52 AM (in response to fjfernandez)The searchfunctionality of the forum can help you. There has been lots of discussion on this subject...
-
3. Re: Problems with conditions in transactions
fjfernandez Oct 10, 2006 7:08 AM (in response to fjfernandez)Thanks for your reply,
I've search before starting this topic, and i've found nothing about this problem. I've found a lot of topics talking about the possibility of adding conditions to transactions or talking about another problems or talking about topics too elaborated for a newbie user, but i've found nothing about a condition that is ignored. Maybe i'm trying a bad search, but i don't think that's the problem. I would be very pleased if you could tell me the topic or just tell me what the problem with my process definitio is. -
4. Re: Problems with conditions in transactions
michaelholtzman Oct 11, 2006 3:25 PM (in response to fjfernandez)The conditional expression must be written in the jBPM "Expression Language", not as a BeanShell (java) snippet as you are doing. See the documentation on decision nodes.
There have been a number of examples posted in this forum. -
5. Re: Problems with conditions in transactions
fjfernandez Oct 16, 2006 4:17 AM (in response to fjfernandez)Thank you very much for replying
Your answer has been really usefull. I know that i can use beanshell for example in events, so i thought the condition should have been writen in that way. That's the reason why i didn't understand the topics i read. I'll following investigating the EL in the conditions.
Thanks again -
6. Re: Problems with conditions in transactions
fjfernandez Oct 17, 2006 5:28 AM (in response to fjfernandez)Hi again,
I've resolved that problem (Thanks again michaelholtzman) but now i've realised that my process variable is allways a String. How can i make it be a long value? An expression like the next one is not very usefull:
expression="#{contextInstance.variables.v eq '100'}"
I need, for example, use something like expression="#{contextInstance.variables.v bt 100}"
The problem is that v is String, so the second exception is allways true or false depending the literal i use.
Thanks in advance and regards -
7. Re: Problems with conditions in transactions
fjfernandez Oct 17, 2006 7:04 AM (in response to fjfernandez)Hi again,
now it's all ok. I've found a sintactic mistake in xml code of jpdl. That was the reason because the decision node wasn't work.