JobDescriptionTranslatorXSLT issue

Added by Alanis Patricia almost 13 years ago

Hi all,

I chose to use the class JobDescriptionTranslatorXSLT for a job plugin, but when I call the method getJobDescriptionTranslator (). translate (doc, jobid) to "translate" a JSDL job in JDF job, I do not get an error but I get a file without the tags which has been declared in the xls file. The strange thing is that I tested my xsl translator by implementing a simple class which recive a jsdl file and give me an jdf file and it works fine.
What am I missing?

Thanks in advace,
Patricia Alanis

xsltranslator.xsl (9.8 KB) xsltranslator.xsl

Replies (3)

RE: JobDescriptionTranslatorXSLT issue - Added by Schwarz Lionel almost 13 years ago

Hi Patricia,
First of all, may I ask you why you want to call the translate() yourself? In principle, once you have declared your translator in the getJobDescriptionTranslator() method, the JSAGA engine triggers itself the translation when you submit a job. The result of this translation is received by the plugin in the submit() method.

Lionel

RE: JobDescriptionTranslatorXSLT issue - Added by Reynaud Sylvain almost 13 years ago

Hi Patricia,

We can generalise what Lionel said to anything in JSAGA : you should use it only through the SAGA API (i.e. interfaces of the "org.ogf.saga" namespace) as much as possible.

For testing your translator without submitting the job, you can use option "-d" of command jsaga-job-run. It will invoke the Job.getAttribute() SAGA method with the non-standard key "NativeJobDescription" (see http://grid.in2p3.fr/software/jsaga-dev/jsaga-engine/xref/fr/in2p3/jsaga/command/JobRun.html#82).

Please let us know if you still have this problem when using your translator this way.

Regards,
Sylvain

RE: JobDescriptionTranslatorXSLT issue - Added by Alanis Patricia almost 13 years ago

Hi all,

I understood what did you said, I will try to do it that way and I'll let you know what happens.

Best Regards,
Patricia

(1-3/3)

Project

General

Profile

JSAGA