hi ya
Ill give that a look mate
nice one estaub
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4083169#4083169
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4083169
___
jboss
harpritt,
Couldn't you copy the value into a process variable, using a task controller?
See http://docs.jboss.com/jbpm/v3/userguide_single/#taskcontrollers
-Ed Staub[/url]
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4079627#4079627
Reply to the post :
htt
Hi estaub
im using SEAM, SESSION scope is one of the contexts that you can work in and is
also made available to the process definition...placing my variab in the
session scope meant that it was available to the node imediatly following the
descision node... as long as the session is not destro
By "session scoped", do you mean "token-scoped" by adding variables to the
process definition, or are you referring to something outside of JBPM?
If you mean "token-scoped", AFAIK this is the standard way to pass data from
node to node. I'm curious - why don't you like it?
-Ed Staub
View the
ive temporaily fixed this by adding a session scoped varaible rather than a
conversational scoped one...
i dont like this ... but it works.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4075872#4075872
Reply to the post :
http://www.jboss.com/index.html?mo
