AW: [geclipse-dev] GRIA questions

["Stuempert, Mathias IWR" <mathias.stuempert@xxxxxxxxxx>]

> Consider this: It has been discussed about removing the job submission
> wizard page that allows a user to select whether it's a gLite job or a
> GRIA job, as it very much depends if we have a gLite compatible VO, or
> a GRIA VO anyway. So surely if we're using JSDL's in a GRIA VO, we
> 'know' it's a JSDL that will be submitted to GRIA, and we could
> perhaps 'disable' certain JSDL fields since they will never ever apply
> in that context.

So what you suggest is similar to a C/C++ editor that should change its
behaviour with the architecture the C/C++ file will be compiled on,
assuming the architecture can be queried from the build/run
configuration the file is currently associated with.

Again, do not put too much magic in g-Eclipse. It will definitely rather
confuse the user. We have a JSDL editor, JSDL is an OGF standard, we are
fully supporting this standard, not more and not less.

What we also support is the submission to different middlewares. Here we
get middleware specific, but not before. Here we have to provide error
reporting and maybe (if possible) validation.

Cheers, Mathias