AW: [geclipse-dev] GRIA questions

["Tao, Jie" <jie.tao@xxxxxxxxxx>]

I was also surprised that users are not allowed to specify what they like in a Gria JSDL. Users, like I, however, are provided with an JSDL editor, where actually they can change everything. The result is: job submission fails and they do not know why. If we can not do anything in the gria side, we have to improve the editor.

Best regards,

Jie 

-----Ursprüngliche Nachricht-----
Von: geclipse-dev-bounces@xxxxxxxxxxx [mailto:geclipse-dev-bounces@xxxxxxxxxxx] Im Auftrag von Mariusz Wojtysiak
Gesendet: Dienstag, 29. April 2008 08:26
An: Developer mailing list
Betreff: Re: [geclipse-dev] GRIA questions

Hello Ken, Ariel, Jie!

Thanks to Ariel for this log fragments! It may help us to discover potential problems.

Ariel Garcia pisze:
> in the tomcat/gria logs i see warnings like this one:
> -----------
> 2008-04-28 07:44:48,547 WARN
> [uk.ac.soton.itinnovation.grid.service.registry.util.content.ServiceEx
> tractionStrategyHelper]
> (Thread-45:DefaultServiceExtractionStrategy.java:56) object '$Proxy10' 
> uses default strategy 'class
> uk.ac.soton.itinnovation.grid.service.registry.util.content.DefaultServiceExtractionStrategy'
> -----------
> what does it mean, is that bad in the sense that the server would like 
> us to use a different "default strategy", whatever that means?

I don't know for what is ServiceExtractionStrategyHelper. Gria documentation says about that class and implemented interfaces exactly nothing (autogenerated java-doc)!

I'm sure Ken may help us to understand why we have this warning on GRIA server.


> Another question:
> i see some exceptions regarding jobs submitted with invalid parameters, 
> things like:
> 
> ** java.lang.IllegalArgumentException: Could not parse JSDL against schema
> (...)
> Caused by: org.xml.sax.SAXParseException: 
> cvc-datatype-valid.1.2.1: 'file:/C:/Dokumente%20und%20Einstell
> ungen/Tao-j/Eigene%20Dateien/geclipse.jpg' is not a valid value 
> for 'NCName'.
> 
> The question is, doesn't the GRIA client libs check for those things before 
> submitting? I think it would make sense that this error is catched by the 
> client libs.

Personally I'm convinced that only GRIA server should make validation. 
There should be only one place where jsdl is validated, to avoid 
consistency problems. Who know - now this jsdl is not valid, but in next 
GRIA server it will be correct?

Please notice that our user (hello Jie :-) saw message "Could not parse 
JSDL..." during submission.

Another thing is that I'm not sure if that error should be logged on the 
GRIA server, because this is not server error. It's rather user's 
mistake, which user may do.

> ** faultString: Application 'paint2' was not found
> 
> ** faultString: Application 'newFile' was not found

> These ones... how can they happen, if we query for the list of available 
> applications in the gria infoservice?
ipse.org/mailman/listinfo/geclipse-dev

We query for list of applications, user may select the correct one. But 
he may also edit application name in jsdl editor.

I see that Jie tested GRIA very deeply! Danke!!!

-- 
Regards,
Mariusz Wojtysiak
_______________________________________________
geclipse-dev mailing list
geclipse-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/geclipse-dev