Re: [geclipse-dev] GRIA questions

["David Johnson" <d.johnson@xxxxxxxxxxxxx>]

2008/4/29 Stuempert, Mathias IWR <mathias.stuempert@xxxxxxxxxx>:
>
>  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.

Yes kind of. But what I'm getting at is that the build 'environment'
(to take the metaphor further) is already defined when we define a VO
in g-Eclipse. There is no querying to know that it's a GRIA job
description JSDL, as it is being created within a GRIA VO to start
with.

Although that said, there might be cases where a user might import
JSDLs into a GRIA VO and then need to modify them in g-Eclipse
perhaps.

>  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.

Sure, I'm out of magic dust anyway.

>  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.

I suppose in a way it's more middleware 'transparent' from the view of
a user rather than middleware specific, since the user will 'submit'
JSDLs and not care if it's gLite or GRIA, even though it's likely they
will know it is gLite or GRIA anyway.

Validation before the actual submission process shouldn't be hard, and
it's something I'm working on with the workflow submission anyway
(which involves JDL validation too).

-David