Hello, We think we have figured out the issue with the encoding. Java Base64 uses a '-' instead of a '+' when encoding. Command line in Linux and Ruby expect a '+'. When we converted the raw Base64 encoded workflow from the android request and changed all the '-' characters to a '+' it works ok. So either we need to figure out how to tell Java to use '+' instead of '-' or we change the encoded workflow string using string replace before adding it to the request string.
Lots of thanks to Finn for helping me to debug this. Cheers, Ian -----Original Message----- From: Larry Akah [mailto:[email protected]] Sent: 07 July 2015 11:37 To: [email protected] Subject: Re: GSOC Taverna Mobile: Uploading workflows to the Taverna player Is it possible that i get the body of the request that the player is actually receiving? Cheers 2015-07-07 11:36 GMT+01:00 Larry Akah <[email protected]>: > workflow id number 34 is the workflow i've been working with > > > 2015-07-07 10:27 GMT+01:00 Ian Dunlop <[email protected]>: > >> Hello, >> >> It's hard to tell from the logs if the output relates to what you are >> doing, what workflow are you trying to upload. The logs are full of >> "parser >> error: PCDATA invalid Char value ". Maybe there are characters in it >> that the tavern player XML parser cannot read. Anyone else have any ideas. >> >> Cheers, >> >> Ian >> >> -----Original Message----- >> From: Larry Akah [mailto:[email protected]] >> Sent: 06 July 2015 17:52 >> To: [email protected] >> Subject: Re: GSOC Taverna Mobile: Uploading workflows to the Taverna >> player >> >> What do the server logs reveal from the recent requests just few >> moments ago? I could use some help from them. >> >> >> Cheers >> >> 2015-07-06 12:22 GMT+01:00 alaninmcr <[email protected]>: >> >> > On 06/07/2015 12:03, Ian Dunlop wrote: >> > >> >> Hello, >> >> >> >> I just sent workflow 16 to the taverna player by base64 encoding >> >> it on the command line and using curl and it all worked ok. Here >> >> is the >> >> base64 version >> >> https://dl.dropboxusercontent.com/u/4958764/wf16.base64 Maybe you >> >> need to ensure it is UTF-8 character set. >> >> >> > >> > Also that it is not broken into lines. That file correctly keeps >> > the >> > base64 all in one line. Some base64 methods will, by default, break >> > it into human-friendly lines which can be confusing for the reading system. >> > >> > Cheers, >> >> >> >> Ian >> >> >> > >> > Alan >> > >> >> >> >> -- >> *Akah Larry N.H* >> >> *Lead Software Engineer @ GiftedMom* >> *Founder IceTeck Inc* >> *www.iceteck.com* >> >> Developing technologies for emergence and sustainable development. >> > > > > -- > *Akah Larry N.H* > > *Lead Software Engineer @ GiftedMom* > *Founder IceTeck Inc* > *www.iceteck.com* > > Developing technologies for emergence and sustainable development. > > -- *Akah Larry N.H* *Lead Software Engineer @ GiftedMom* *Founder IceTeck Inc* *www.iceteck.com* Developing technologies for emergence and sustainable development.
