JSAGA WMS ADAPTOR - Problem with EMI-3 WMS
in the last days we started to use some WMS based on EMI-3 release.
We were able to submit jobs towards EMI-3 WMS but we couldn't properly check the job status.
In particular, when we tried to get the job status we got the following exception:
NoSuccess: org.xml.sax.SAXException: Invalid element in org.glite.wsdl.types.lb.JobStatus - pbsSubstate
Checking the state of the same job by command line in a UI, we were able to properly read the job status.
Instead using EMI-2 WMS everything worked well.
Do you have any idea about this behaviour?
Hi Diego, yes I have indeed an idea of the problem, it seems the wsdl changed between EMI-2 and EMI-3, so the answer sent back by EMI-3 WMS is not compatible with what JSAGA expects anymore.
I'll come back to you soon, to try to make JSAGA WMS adaptor compatible with EMI-3.
I'm currently testing the component developed by Diego with the newest version of jSAGA (0.9.17).
Despite everything was working properly with the older version (0.9.16), now we have a problem getting the job status and searching in google with the log I found this old thread. Indeed the error is the same. After a deeper look to the library list, I noticed this difference between the two jSAGA versions:
glite-lb-api-java-3.2-p1.jar --> glite-lb-api-java-3.3.1.jar
Attached you'll find the entire log.
Any suggestions on the error?
Thank you for your help.
pbsSubstate.log (6.27 KB)
Normally, if you have the latest 0.9.17 snapshot
, you should be on glite-lb-api-java-3.3.2 (which I think has the same problem though).
Could you check and try with 3.3.2?
Hi Lionel, thank you for your reply.
I tried to find the lib for that version but with no results.
I searched in the emi web sites but I didn't find the corresponding package. It should be probably here:
but I have no idea in which rpm the suggested version is located.
Do you know where I can find the jar?
Riccardo, in fact, the lib is build inside JSAGA from WSDL files. I have just published the 3.3.2 in our Maven repo:
Riccardo, I just tested and checked that this is indeed fixed with this external lib: