Hi Joerg, I believe adding a trim shim is the best way to go. We cannot make any assumptions about what data goes into a REST service - some users may want to add a "\n" in their input and that is valid input, too.
Regards, Alex On 20/05/2011 11:09, Joerg Wicker wrote: > Hi again, > > Alan R Williams<[email protected]> writes: > >> On 19/05/2011 17:56, Joerg Wicker wrote: >>> I attached an example workflow. The REST service copy_dataset gets a >>> string constant as input and returns a URL. When I pass the URL to the >>> next REST service (merge_datasets), I get the >>> IllegalArgumentException. But if i pass the same value using a string >>> constant to merge_datasets_2, a copy of merge_datasets, everything >>> works well. >> They aren't the same value. The output from merge_datasets includes a >> "\n" at the end, whereas val_of_debug3 does not. >> >> It's not legal for a URL to contain "\n" so the exception is generated. >> >> I don't know if it is Taverna's REST service that is wrong in generating >> the URL with the "\n" or if it is the remote resource that is incorrect. >> I'll ask a REST expert. > I think it's from our servces. Unfortunately some servers add a > newline at the end, some don't. I forgot to check that. Is there any > better solution than adding a Beanshell service doing a trim()? I > doubt I can make every partner here change their server to return a > result without a newline. > > Thanks and regards, > > Joerg > > ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
