Contributions
Re: Invalid date value in SOAP Response
Thanks for your help but I still have the same error message with this syntax. I've also tried with the other value like heartBeatInterval and I also have the same kind of error. What does SoapUI check to say thsi is an invalid date value ? Regards, Xavier5.6KViews0likes6CommentsRe: Invalid date value in SOAP Response
Hi, The SOAP mock response The test case The overview of the project. I've tried different syntax for "dateTime" and nothing seems to work. "2019-01-29T14:45:32.345Z" => Invalid date value '2019-01-29T14:45:32.345Z' => Invalid date value 2019-01-29T14:45:32.345Z => Invalid date value5.6KViews0likes8CommentsRe: Invalid date value in SOAP Response
Unfortunately it doesn't workeither. Invalid date value: ${#Project#dateTime} <ns:bootNotificationResponse> <ns:status>Rejected</ns:status> <ns:currentTime>${#Project#dateTime}</ns:currentTime> <ns:heartbeatInterval>60</ns:heartbeatInterval> </ns:bootNotificationResponse>5.7KViews0likes10CommentsInvalid date value in SOAP Response
Hi, I've got difficulties to use properties in a soap response. When using this syntax: <ns:currentTime>2019-01-29T14:45:32.345Z</ns:currentTime>, no problems the syntax is Valid regarding the wdsl file given to SoapUI. I try to replace the fixed string2019-01-29T14:45:32.345Z by a project property defined as: Name = dateTime and Value =2019-01-29T14:45:32.345Z And use it like this <ns:currentTime>${Project#dateTime}</ns:currentTime> The result is Invalid date value: ${Project#dateTime} ns:currentTime is an xmls:dateTime Where do I make a mistake ? Thanks.Solved6.2KViews0likes12Comments