The ant scripts were written to just start and stop. To send messages they would need to run concurrently and on different ports, which would then break if they were run in isolation. I tried to keep the whole simple enough so ant run does unit test and java command does system test. But we can 'fix' this in the next release if necessary.
On 11/6/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > Ignacio Silva-Lepe wrote: > > Hi JS, > > > > The binding-notification-* samples can be run in isolation via ant run. > > But also to run them from the command line, they assume that the > > ntm runs on port 8083 and so the sample that is started first needs > > to use that port. The sample command in the README for the > > producer does that, so if you use it you should run the producer first. > > Otherwise, just make sure that the first one you run uses > > -Dnotification.httpPort=8083. The sample overview in the READMEs > > tries to describe this. > > > > > > > [snip] > >> - All standalone samples with ant scripts worked except the > >> binding-notification-* ones as I didn't know in which order I was > >> supposed to start them. Just one minor issue: the nodes in > >> calculator-distributed did not exit after pressing enter, but ctrl+C > >> worked :) > >> > >> > OK, I got the binding-notification producer and consumer working, using > the java... command lines described in the READMEs. However the ant > scripts seem to just start + stop each sample without giving the > opportunity to send messages. This is not a blocker though, they can be > fixed in the next release. > > -- > Jean-Sebastien > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
