#111 parameter can not have 'xml' in name

0.60
closed-invalid
5
2007-10-03
2006-08-14
jason zhaao
No

Hi, All

I have a simple soap client call like this
$server->blastall_simple(
SOAP::Data->name("blastall")->value("blastx"),
SOAP::Data->name("query")->value("binaryfile"),
SOAP::Data->name("protein_db")->value("ecoli.aa"),
SOAP::Data->name("nucleotid_db")->value("ecoli.aa"),
SOAP::Data->name("xml_output")->value("myoutput.xml"),
SOAP::Data->name("tmp_outfile")->value( $query_id .
".blastx" ),
SOAP::Data->name("view_alignments")->value( 7 )
);

When I run this command, I got this error: Element
'xml_output' can't be allowed in valid XML message. Died.
If I changed the parameter name from "xml_output" to
"output", the call was ok.
It seemed that the soap-lite implementation prevented
"xml" substring in parameter name.

-jason

Discussion

  • Martin Kutter

    Martin Kutter - 2007-10-03
    • assigned_to: byrnereese --> kutterma
    • status: open --> closed-invalid
     
  • Martin Kutter

    Martin Kutter - 2007-10-03

    Logged In: YES
    user_id=884175
    Originator: NO

    This is perfectly correct, as the XML standard prohibits the use of "xml" as start of XML tagnames. You should refine your webservices, as it demands for invalid XML.

     

Log in to post a comment.