2009/2/25 Tammo van Lessen <[email protected]>: > Paul Brown wrote: >> >> Hi, Rafal -- >> >>> what do you think of implementing a command line tool bpelrun, which >>> could compile and run a process by sending a request from stdin and >>> displaying response to stdout. >>> This would speed up testing of various bpel constructs. It would be >>> helpful in developing larger processes by copy-pasting from small >>> examples. >>> It could be also useful to do bpel unit testing. >> >> Great idea. I'd thought about doing something similar once upon a time, >> making a kind of "busy box" for a process instance where you could drop >> messages onto ports and see them show up where they come out. > > Yep, that's a funny idea. I just imagine to compose a pipes-and-filters > architecture with BPEL on the console with pipe-operators :) > > One important thing to bear in mind: BPEL processes are not necessarily > single-entry-single-exit processes so that just using stdin and stdout > won't work for async processes or processes that expect input from > different operations and/or partnerlinks.
That's true. However they can always be invoked by another single-entry-single-exit wrapper process. And as for piping, this is really cool idea :-), because it enables division of testing and tested bpel code into two instances. I think it's possible to do an ode-standalone package, which could make use of current ode-axis2-war testing code, which actually does that. I think two axis2 instances can be piped up using soap ws-addresing requests without even http. This idea is quite realistic to implement :-) -- Rafał Rusin www.mimuw.edu.pl/~rrusin
