[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-02 Thread kukeltje
Within the company I work for, We've done this (a process as your describe) with the jbpm async support (so no jms of our own). In that situation it just works, both with jms or the proprietary jBPM queue thing... For us there was no need to develop some thing like this ourselves. View the orig

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-02 Thread unome
anonymous wrote : | Question: Do you save the PI after signalling it to go into the fork? I assume you do, but just want to be sure. | | Earlier I was not. Shame on me. I had a "State" node earlier. To make things easy I changed it to a Task-node and let the webapp handle the save (usin

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread kukeltje
anonymous wrote : So one child token goes to a "node" while the other still goes to a "task-node". And then I added the action to the node instead of the event "node-enter". But I still see the same results. ok, thanks for trying anonymous wrote : i.e. If I manually (via the webapp) "Save and

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread unome
Ronald, This is what I attempted: I changed the "State" node "StateA" to a "node" node. i.e: So one child token goes to a "node" while the other still goes to a "task-node". And then I added the action to the node instead of the event "node-enter". But I still see the same results. i.e. If I

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread kukeltje
I looked at your code and see that you use a static for the JbpmConfigiration. Good, so that part is optimized. It could still be that since your code runs on the node-enter, that the async stuff is to quick and tries signalling the node/token while it is not persisted. Strange behaviour could

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread kukeltje
creating the JbpmConfiguration each time is SLOW and should not be done. That is why I said that if you want ASYNC functionality look at what jBPM provides for you there, either custom or JMS based. That is optimized! View the original post : http://www.jboss.com/index.html?module=bb&op=viewt

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread unome
Should I not be creating the JbpmConfiguration in the MDB and then getting the JbpmContext? Is there a JbpmConfiguration created by the webapp that I should be using for creating JbpmContexts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962215#3962215

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread Olivier_Debels
You're right! It only goes for nodes that don't override the execute method (simple nodes f.e.). So forget my remark for this one. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3962120#3962120 Reply to the post : http://www.jboss.com/index.html?module=bb&o

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread kukeltje
@Olivier: That is not true for states, tasks, etc... only for nodes that have no implementation (custom nodes) AFAIK. @unome: Yes, there is more to it. States etc have implementations do not expect to be signalled on events. De behaviour you get when signalling nodes in an event is undefined

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-08-01 Thread Olivier_Debels
A remark that maybe can help: If you are creating action handlers on node events (like in your case where you have ExternalServiceActionHandler on a node-enter event) you don't need to call node.signal(). The reason for this is that by default node.signal() will be called in the action of the

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-07-31 Thread unome
I don't think the MDB runs in the transaction created by jBPM. But I'm not sure since I'm still picking up on jBPM. Maybe you are referring to the JbpmContext I create in the MDB to load the token and signal it. The MDB is started when JBoss starts up. It's subscribed to a JMS Topic. The Extern

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-07-31 Thread kukeltje
Could it be the mdb runs in the transaction created by jBPM? In that case the behaviour you see may be slithgly explained. You signal the stateA in it's own node-enter, wich is not advised. If you can look into this, we can go further from there. could you create a pd.xml with the classes and

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-07-31 Thread unome
Another interesting behavior I noticed: If the MDB "signals" before the task-node is completed, the processing goes to join but realises that it cannot complete since the other token is still active. But on completion of the task, processing does not resume at join. It says that other token (to

[jboss-user] [JBoss jBPM] - Re: monitoring piece of default webapp not displaying the co

2006-07-31 Thread unome
I'm also using ehcache-1.2.jar instead of ehcache-1.1.jar that comes bundled with the jbpm starter kit View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3961956#3961956 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3961956