myGrid

xsd:decimal and xsd:dateTime not recognised as types

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.4, 1.5
  • Fix Version/s: 1.5.1
  • Component/s: Taverna Processors
  • Labels:
    None

Description

Taverna, and ultimately the WSDL processor does not recognise the types xsd:decimal and xsd:dataTime included in the wsdl:
http://www.weather.gov/forecasts/xml/SOAP_server/ndfdXMLserver.php?wsdl
so treats these as XML by default. This appears to cause the SOAP message to be incorrectly generated causing an error calling the webservice.

Taverna needs fixing to recognise these types, and also it would seem logical to use the WSDL parsing to recognise base types and treat them as text/plain rather than text/xml.

Activity

Hide
Stuart Owen added a comment - 2006-11-23 16:27

And also xsd:integer

Show
Stuart Owen added a comment - 2006-11-23 16:27 And also xsd:integer
Hide
Stuart Owen added a comment - 2007-01-08 16:47

This should now be fixed. The types decimal and integer have been explicity defined for the correct type. Other unrecognised types, that the parser has recognised as a Base Type are treated as String.

Show
Stuart Owen added a comment - 2007-01-08 16:47 This should now be fixed. The types decimal and integer have been explicity defined for the correct type. Other unrecognised types, that the parser has recognised as a Base Type are treated as String.

People

Vote (0)
Watch (0)

Dates

  • Created:
    2006-10-19 15:12
    Updated:
    2007-01-08 16:47
    Resolved:
    2007-01-08 16:47