AW: [geclipse-dev] A question to workflows

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

> g-Eclipse does not and should not orchestrate or manage the workflows,
> as that's what the middleware does. This is the case with gLite, and
> the failing behaviour Mathias originally described is most likely
> purely up to gLite. I think the JDL is probably correct, but obviously
> we can't discuss this unless you post the JDL to look at.

Create a WF with the editor, Create three WF jobs in there, A, B, C.
Make B depend on A and C on B. Link any JSDL (e.g. simple_hostname) to
them, that's it!

> Indicating how the middleware should deal with cases would be nice,
> but if we introduce these kinds of parameters into a workflow, there
> will never be a guarantee a middleware's workflow engine will support
> it. In particular, we need to ask if gLite supports this kind of
> specification of workflow job criticality, along with GRIA's way of
> doing things. Off the top of my head, I'm not sure they do.

This is why I was asking. I am just the dump user and wanted to have
this clarified. And furthermore, if this is bad gLite behaviour, we
should report this to the gLite guys. But before we should be really
sure that it is bad gLite behaviour. So please check this!

Cheers, Mathias