"mputz" wrote : we've experienced problems with special characters in
node-names on Windows machines already, please check out
http://jira.jboss.com/jira/browse/GPD-98 whether your problems are similar.
I have at least a partial resolution to this problem (for scandic letters):
Change both gpd.x
"mputz" wrote : we've experienced problems with special characters in
node-names on Windows machines already, please check out
http://jira.jboss.com/jira/browse/GPD-98 whether your problems are similar.
Ok. Thanks for information! I tried to search topics with error message but
couldn't find an
I'm getting this error in jbpm-console when i'm trying to watch the process
image:
Error getting diagram info: An exception of type "org.jbpm.util.XmlException"
was thrown. The message is: couldn't parse xml
The image is OK but I don't see the red borders on current token. The error
seems to
I'm terribly sorry. The state node requires signal in server environment also.
Now that I tested more, I noticed that half of my processes doesn't end. The
problem was, they most of time threw exception before the state node and this
thing took my eye off from process state.
Case closed and I'm
I'm a bit confused about signaling the process. I have used few simple
processes and I have used state-nodes with them. But I don't recall signaling
after those nodes and they have worked as NOT wait states. But now that I
started testing similiar cases, I have to give signal to the process in o
Thanks mate! The problem wasn't with signalin but using the handler. I had
ACTIONhandler in action node-enter where I used leaveNode method rather than
DecisionHandler. It's fixed now. Sorry for my stupidness :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4
Seems nice. Just by curiosity, why you put all to that one variable? You could
have made two variables:
that is VAR, CONST or FUNC and
that is the data used as parameter
what I'm interested in, what did you do after this? did the process do
something different depending the result?
View the o
I made more research with this problem.
It seems, that when the process ends, it executes the second node - the not
selected path (the one I didn't go to from decision). The reason it executes
the not selected is that it is the default transition from decision node.
I made a test case that simp
update to problem:
If i don't use the join node (well, even if i do use this happens), both paths
are still ran.
|
|
|
| SomeName
|
|
|
|
|
|
|
|
|
|
|
I want to select a path depending on a value from database. All goes smooth
until I have selected the path. I want to run the path I have selected but not
the other path. If I simply make a transition to end node from both paths, it
almost works. The problem is, the path I didn't select, didn't
Yep.. the problem is that documentation doesn't follow the written code. And
user guide isn't up-to-date anymore. And user forum has old tips. This is quite
common problem in (os) projects that are in constant progress. I think it
creates a bit of confusion and this is one reason why open source
Ok. I know that this is propably the wrong place to talk about the forum
itself. But I couldn't find a place to talk about it elsewere :S
So, I've been testing Jbpm 3.2.1 for a while and noticed that the documentation
is not up to date. I've been using this forum to get help but tips are usually
Sorry but I can't help any further. Maybe you should ask this from hibernate
forum..
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068604#4068604
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068604
_
try using this code:
| ProcessInstance process = ctx.newProcessInstance("ProposalToOrder");
|
instead of creating graphsession etc..
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068599#4068599
Reply to the post :
http://www.jboss.com/index.html?modul
I had to copy C:\jboss\jbpm-jpdl-3.2.1\deploy\jbpm-enterprise.ear to
C:\jboss\jbpm-jpdl-3.2.1\server\server\jbpm\deploy
Still this doesn't work but at least the error message changed. It's sorry to
see that newer versions of jBPM isn't always compatible with older versions. In
my opinion, this
I'm trying to test 3.2.1 version and deployed a war file (that i have used for
testing with 3.1.3 jbpm-starter-kit) that included simple servlet that created
a new process instance. Servlet throws following error:
10:28:54,020 ERROR [[XmlReceiver]] Servlet.service() for servlet XmlReceiver
thre
16 matches
Mail list logo
