Re: AW: [geclipse-dev] GRIA questions

[Ariel Garcia <garcia@xxxxxxxxxx>]

Hi all,

> > > The question is, doesn't the GRIA client libs check for those things
> > > beforesubmitting? I think it would make sense that this error is
> > > catched by theclient libs.
> >
> > That bring us to the point of validating the JSDL for GRIA. We cannot
> > prevent user from editing JSDL - we have a general editor for those 
> > files, and at the point of editing a JSDL file is only a JSDL file.
>
> I fully agree with Kasia, don't put too much magic into g-Eclipse. The
> user is always able to create/edit any type of job description for any
> type of middleware that will fail miserably. So in any case we have to
> submit and wait for the result. If something fails then we hopefully get
> an error message from the server side. If we do not get something like
> that we can still make use of the problem reporting mechanism.

well, me too i fully agree with that.

Notice that i was not proposing to add magic on the gEclipse side, i was 
asking why the gria CLIENT LIBS were not taking care of that :-)

We do not deal directly with the gria server, we delegate the job to the 
gria libs. And when the libs get the JSDL for submission, they could:
 - do syntax-validation (no use to submit to the server a JSDL which has a 
field which is not accepted/recognized by GRIA, missing dataStagers, 
etc ). Will the libs accept to submit to the server a txt or jpg file we 
give them as jobdescription? i guess/hope not... :)
 - possibly also do some kind of dynamic validation (the libs already know 
to which exact server the JSDL is being submitted, and if i remember 
correctly they store some session information, i mean the list of 
applications in the server is probably already cached in that session...)

Anyway, regarding the other points discussed in the same thread

 +2 the JSDL is JSDL is a standard
 +2 the jsdl editor only deals with that standard
 +1 either we or the gria client libs do some (offline) syntax validation
     _outside_ the editor when the user tries to submit it.

Cheers, Ariel