Re: [Myexperiment-discuss] change or bug in the read-workflow rest API?

[Don Cruickshank]

The problem is now resolved.

Many thanks,
Don.

> -----Original Message-----
> From: address@hidden
> [mailto:address@hidden
> On Behalf Of Don Cruickshank
> Sent: 20 September 2012 2:23 PM
> To: Mark Thompson; address@hidden
> Subject: Re: [Myexperiment-discuss] change or bug in the read-workflow
> rest API?
> 
> Hi,
> 
> This is not a change in the REST API.  It's a bug that we're now looking into.
> 
> Thanks for reporting it!
> 
> Regards,
> Don Cruickshank.
> 
> > -----Original Message-----
> > From: address@hidden
> > [mailto:myexperiment-discuss-
> address@hidden
> > On Behalf Of Mark Thompson
> > Sent: 20 September 2012 11:48 AM
> > To: address@hidden
> > Subject: [Myexperiment-discuss] change or bug in the read-workflow
> > rest API?
> >
> > Hi,
> >
> > I'm maintaining an application (t2-web) that depends on the
> > MyExperiment REST-API. It was working fine until recently. In the XML
> > output of "read workflow" it looks for an element <components> should
> > contain information about the inputs and outputs of a workflow as
> > <source> and <sink> elements.
> >
> > However, if I look at the output of:
> >   http://www.myexperiment.org/workflow.xml?id=74&all_elements=yes
> > then the <components> element is empty. Actually, I tried a few
> > different Taverna workflows, and <components> is always empty.
> >
> > Is this a bug in the rest-api XML output, or has the API changed recently?
> >
> > Regards,
> > Mark Thompson
> >
> > _______________________________________________
> > Myexperiment-discuss mailing list
> > address@hidden
> > https://lists.nongnu.org/mailman/listinfo/myexperiment-discuss
> 
> _______________________________________________
> Myexperiment-discuss mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/myexperiment-discuss