Re: AW: [geclipse-dev] Separating geclise grid model from eclipse worksp

["Katarzyna Bylec" <katis@xxxxxxxxxxxxx>]

Hi Romain,

> > job description is a job description and it's a file rather than sth  
> > that exists independently from resource.
>  From my point of view that is not right. If a job description is a file  
>  it should inherit from that class and that is not the case.
When you mentioned it - in fact JSDLJobDescription has a class based on  
IResource in its hierarchy (ResourceGridContainer, though  
IGridJobDescription doesn't). Anyhow - there is also one more point where  
this class is bounded to resources - it's EMF's notifications, on which  
the JSDL Editor is build. Also the easiest way of loading EMF's model is  
to do it from a file (to make things even more complicated this is - EMF's  
resource, not Eclipse's ;)).

> Furthermore when you submit a job to submission web service you submit a  
> string.(...)
> So a job description is not a file, neither a string, for me it is a job  
> description.

Yes, also for me is a job description, but seen in terms of persistence -  
a file, and - in g-Eclipse it's also a file (no matter - Eclipse's or  
EMF's one).
If we decide on string serialization to file when needed, we may end up  
making this very often in g-Eclipse. So - as I said before - that's not  
the direction this discussion should go in. We should rather seek for a  
way to make the persistence of JSDL kind of transparent.

Kasia