Re: AW: [geclipse-dev] Testing Services

[Ariel Garcia <garcia@xxxxxxxxxx>]

Hi,

> /**
>  * Get the result of the last validation process.
>  *
>  * @return True if the last call to #validate() returned without
>  * throwing an exception, false otherwise.
>  */
> public boolean isValid();
>
> The first method could be bound to an appropriate action in the Grid
> project view's context menu. The second method could be used by the Grid
> project view in order to mark a service as invalid. The advantage of

then i would propose to change to a more "fault tolerant" method:

/**
 * Get the result of the last validation process, if any was performed.
 *
 * @return True if the last call to #validate() found the resource to be
 * not working correctly, false otherwise.
 */
public boolean isInvalid();

The advantage would be that if the user didn't test the resource 
   (which would be the normal case, he won't test all resources every
    time s/he starts geclipse)
he would still get a "normal" icon for the resource. And only if s/he 
actively tested the resource and that gave failed then the icon is changed 
to "red".

Even better would be a tri-valued status,
 - untested
 - tested and OK
 - tested and BAD
something like:

/**
 * Get the result of the last validation process, if any was performed.
 *
 * @return STATUS_UNTESTED if the resource was not tested yet,
 *              STATUS_OK if the last call to #validate found the resource
 *                                  to be working fine,
 *              STATUS_BAD if the last call to #validate found the resource
 *                                  to be not functioning.
 */
public ResStatus getStatus();

where
  enum ResStatus { STATUS_UNTESTED, STATUS_OK, STATUS_BAD }

Cheers, Ariel