RE: Event Listeners

This may be the answer you're looking for...When you call
executeCommand(Command ) on your Client instance, that method returns a
boolean.  I seem to recall seeing that the boolean indicates success or
failure of the command.  However, I cannot find where I think I saw that,
and oddly enough it doesn't appear to be in the javadoc for that method, so
obviously you should test it out.

-David

-----Original Message-----
From: Keith Schomburg (kschombu) [mailto:[email protected]] 
Sent: Tuesday, August 16, 2005 5:56 AM
To: Milos Kleint; [email protected]
Subject: RE: [javacvs-dev] Event Listeners


I assume you mean the MessageEvent.isError() method indicates whether output
should be sent to stdout or stderr?  This is where the confusion comes in as
the name isError implies that the result indicates whether the message is an
error or not.  The behavior is different than one would expect given the
name.

In light of this, how does one programatically using cvsclient determine if
a given command (e.g. add, commit, remove, etc.) was successfully executed
by the server?

Thanks,
  Keith 

> -----Original Message-----
> From: Milos Kleint [mailto:[email protected]]
> Sent: Tuesday, August 16, 2005 2:49 AM
> To: 
> Cc: Keith Schomburg (kschombu)
> Subject: Re: [javacvs-dev] Event Listeners
> 
> well, the client cannot really distinguish what is error and what is 
> not. The server reports the problem as either stdout or stderr. That's 
> what the events mirror. all you could do is come up with some pattern 
> based heiristics to figure out the "non"-errors.
> 
> Milos
> 
> On 8/11/05, Keith Schomburg <[email protected]> wrote:
> > How do you distinguish a MessageEvent received by an event
> listener as
> > truly an error message?  I noticed that all status type
> messages (e.g.
> > "cvs add: scheduling file ...", "cvs update: Updating ...",
> etc.) are
> > received and tagged as an error.  I would not classify these type 
> > messages as error messages.
> > 
> > Keith
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> > 
> >
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]