similar to: help with SSOAP (can't find working examples)

Dear all, I've been trying on and off for the past few months to get SSOAP to work with chemspider. First I tried the WSDL file: cs<-processWSDL("http://www.chemspider.com/MassSpecAPI.asmx?WSDL") Error in parse(text = paste(txt, collapse = "\n")) : <text>:1:29: unexpected input 1: function(x, ..., obj = new( ? ^ In addition:

Hi, I am trying to create a BioMoby client in R using SSOAP. BioMoby is a normal SOAP web service, with request and response messages wrapped in BioMoby XML dialect. Since the particular WSDL I am having problems with is autogenerated and used similarly by *many* services, it would be quite important to a) fix SSOAP or b) fix the WSDL generator. I am a bit lost how to continue debugging

Hi again, On Tue, 2010-06-22 at 10:02 +0200, Steffen Neumann wrote: > So, if XMLSchema:::processSchemaTypes() does not find > any custom/embedded type definitions, is it possibe to "inject" those > from the http://www.w3.org/2001/XMLSchema.xsd > into genSOAPClientInterface() instead ? Well, it's not possible, at least for me. This is as far as I got, any help

Dear list, I've been using R for a while, but am new to web services. I'm a relatively novice programmer; advance apologies for incorrect terminology. I'm trying to send queries and get results back from a SOAP server, using the SSOAP package. My code contains sensitive API keys and URLs, and unfortunately I'm unable to share it uncensored. I have not been able to reproduce the

Dear community, has anyone managed to get SSOAP working with the ChemSpider Web APIs, using functions which need the security token? I use SSOAP 0.9-0 from the OmegaHat repository. In the example code from SSOAP there is a sample which uses a token function. Interestingly, it checks if(!is.character(token)) first (and proceeds if the token is NOT character.) I can't test that function since I

Hi, so, last post from here unless I can provide any more input to fix the upstream package. On Tue, 2010-06-22 at 10:02 +0200, Steffen Neumann wrote: > So I got a bit further, the reason for the error is > that the WSDL *does not have* any <wsdl:types>...</wsdl:types>, I created a local copy and inserted a dummy <wsdl:types>...</wsdl:types> element. Then, my