[MOBY-l] MOBY tutorial - Taverna

[Edward Kawas]

Sorry about the previous message. I was 'misread' the workflow. The articlenames
are set correctly. So I don't know why one works over the other. 

How did you generate the service provider code?

Eddie 

> -----Original Message-----
> From: moby-l-bounces at lists.open-bio.org 
> [mailto:moby-l-bounces at lists.open-bio.org] On Behalf Of Nassib Nassar
> Sent: Thursday, November 02, 2006 11:58 AM
> To: moby-l at lists.open-bio.org
> Subject: [MOBY-l] MOBY tutorial - Taverna
> 
> (Thanks to Paul for the test client fix.)
> 
> I'm having trouble using the ConvertAAtoFASTA_AA servlet 
> example from within Taverna.  I made a simple workflow to 
> test this, and everything works perfectly if I send the 
> biomoby service a fully formed XML input but not if I build 
> the input using biomoby processor objects.  The workflow runs 
> both cases in parallel:
> 
> Workflow:      http://nassar.europa.renci.org/biomoby_aa2fasta.xml
> Inputs:        
> http://nassar.europa.renci.org/biomoby_aa2fasta_input.xml
> Error detail:  
> http://nassar.europa.renci.org/biomoby_aa2fasta_error.xml
> 
> The error is "Task failed due to problem invoking biomoby service. /
> SAXParseException: Premature end of file."  Tomcat's log 
> reports non-XML in the SOAP message (and it actually appears 
> to be non-ASCII).
> I also see differences in the input XML constructed by the 
> AminoAcidSequence object, such as missing articleName='inseq' 
> in element moby:Simple.
> 
> I've tried this with the Taverna 1.4 release, the stable 
> snapshot from October 2, and recent builds from cvs 
> (hopefully including the newer biomoby plug-in module), and 
> it seems I get the same results in all cases.
> 
> Maybe I'm building the input objects incorrectly?
> 
> Nassib
> _______________________________________________
> moby-l mailing list
> moby-l at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-l