Forgot to attach the code. You can download it on the link i gave. Cheers, Francois.
On 8/2/07, Francois Hornoy <[EMAIL PROTECTED]> wrote: > > > Hi, > > I have a basic Java GRAM Client (code attached), based upon globusrun > code. > > When submitting a job in bacth mode (the submitting returns instantly, > and we get a "job handle" as return), we don't wait (as it returns > instantly). > > In non batch mode, the call is blocking. There is this "stateChanged" > callback function that is called each time the status of the job changed > (and for example, we can delete the job when it's "done") and prints the new > status (try the code). > > According to the author of the code, in batch mode, the callback function > is not called and so on... (we don't wait, we don't received the state > changes, etc..). So to be aware of the state of the job, we must "pull" it, > with the "job handle" given. But how to have a "push" way, like in non-batch > mode? I mean, can we submit 100 jobs in batchmode, and a callback function > called each time the state of a job changes ? > > My unexperience may make my ideas not clear, sorry for that. :-) > > Here is the link of the IBM tutorial, and the code attached. > http://www.ibm.com/developerworks/grid/library/gr-wsgram/index.html > > Best regards, > Francois. > > On 8/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Francois, > > i think i don't understand what you want to do. > > Can you try to explain it a little more, please? > > What should be done in batch mode and what exactly is > > batch mode for you? > > What exactly do you mean by "starting my batch mode"? > > Martin > > > > > Hi, > > > > > > I have a simple GRAM Client in Java. It implements the > > GramJobListener > > > interface, so that in interactive mode, with the callback function > > > "stateChanged", i can cacth the changes in the state of the GramJob, > > and > > > destroy the job when it's "done". > > > > > > But i would like to do exactly the same in batch mode. I mean, > > launching > > > my > > > batch mode, and getting the output/destroying the job when it's > > "done". > > > Can > > > we use that "stateChanged" callback too? Is there another way to do > > that? > > > > > > > > > Cheers, > > > Francois. > > > > > > > > > >
