Perhaps I should send along a POJO which keep track of values associated with a thread id?! Just thought of that option...
Christian Karlsson CAG Contactor AB Adress: Jan Stenbecks Torg 17, SE-164 40 Kista Mobil: +46 (0)706694527 Mail: christian.karlsson <at> cag.se www.cag.se<https://wmail.cag.se/owa/redir.aspx?C=G2EjVQkj7kGZyieqy24uGB6NV2uAkM9Iy3xqV4cZFUaEVGXCGlWIq_V5O25t1jIUtjHgAaGFl0U.&URL=http%3a%2f%2fwww.cag.se%2f> Från: Karlsson Christian [mailto:[email protected]] Skickat: den 18 april 2013 15:27 Till: [email protected] Ämne: [jbehave-user] Setting up parallell stories with Spring configured Steps classes Hi all I have a situation where I test a workflow of a case in our application. Until now I've used static variables to keep track of the case id and some other information. (I know it's not the "right" way to do it but it was convenient :) Since some of the scenarios requires the processing to suspend for a few minutes (we are waiting for a BPEL process to finish) I now feel the need to run stories in parallel. I've seen the noughtsandcrosses example which passes the WindowControl to all Step classes. But how would you set this up when you have your steps in the Spring configuration XML? Feel a bit puzzled here and any advice would be appreciated. So far I either have the same case id for all stories (using static variables) or can't pass values along at all :( I guess I need to prototype the beans in the XML but then what? Well, I'll keep digging. Happy coding, Regards Christian Karlsson CAG Contactor AB Adress: Jan Stenbecks Torg 17, SE-164 40 Kista Mobil: +46 (0)706694527 Mail: christian.karlsson <at> cag.se www.cag.se<https://wmail.cag.se/owa/redir.aspx?C=G2EjVQkj7kGZyieqy24uGB6NV2uAkM9Iy3xqV4cZFUaEVGXCGlWIq_V5O25t1jIUtjHgAaGFl0U.&URL=http%3a%2f%2fwww.cag.se%2f>
